- Notifications
You must be signed in to change notification settings - Fork4
Failover support#98
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
25a9a9d to12a6ec4CompareUh oh!
There was an error while loading.Please reload this page.
851d59f to507beacCompareUh oh!
There was an error while loading.Please reload this page.
zhiyuanliang-ms commentedOct 21, 2024 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
How about seperating this PR into two smaller PR to make it easier to review. For example, the change of adding client manager can be a seperated PR and I can approve it quickly. And with client manager change merged, it won't block the following new feature like snapshot support. |
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
32bf44b to3d95750CompareUh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
3b563d8 to1ea1d51Compare7db665f intopreviewUh oh!
There was an error while loading.Please reload this page.
| functionisFailoverableError(error:any):boolean{ | ||
| // ENOTFOUND: DNS lookup failed, ENOENT: no such file or directory | ||
| returnisRestError(error)&&(error.code==="ENOTFOUND"||error.code==="ENOENT"|| |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
https://nodejs.org/api/errors.html#common-system-errors Missed some error type
Uh oh!
There was an error while loading.Please reload this page.
Replica Auto-Discovery: For App Configuration stores with geo-replication enabled, the provider will now automatically discover any additional replicas and attempt to connect to them when it fails to connect to user-provided endpoints in code. This capability allows applications to leverage geo-replication for enhanced resiliency without code change and redeployment. Replica discovery is enabled by default and can be disabled by setting the new AzureAppConfigurationOptions.replicaDiscoveryEnabled property equal to false.
Usage:
Note:
Replica discovery can only work in node.js environment.