Skip to content
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 our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG]: Handling 403:1008 for address resolution calls. #4710

Open
Tracked by #4703
jeet1995 opened this issue Sep 19, 2024 · 0 comments
Open
Tracked by #4703

[BUG]: Handling 403:1008 for address resolution calls. #4710

jeet1995 opened this issue Sep 19, 2024 · 0 comments
Assignees

Comments

@jeet1995
Copy link
Member

We are continuously addressing and improving the SDK, if possible, make sure the problem persist in the latest SDK version.

Describe the bug
When a region has been removed and the SDK possibly reaches out to removed region and performs address resolution calls against the removed region could have the operation fail.

To Reproduce
Use the chaos framework in the Gateway mode to inject 403:1008s for Address resolution requests [or] subject a workload to single-write multi-region account where the write region is failed over.

Expected behavior
Ideally, address resolution in-lined with the document operation should be part of the document operation's ClientRetryPolicy and be retriable to other available regions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants