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

[FEATURE REQ]Immediately trigger cross-regional fail-over on 410/LeaseLost #39557

Open
2 tasks done
FabianMeiswinkel opened this issue Apr 4, 2024 · 1 comment
Open
2 tasks done
Labels
Client This issue points to a problem in the data-plane of the library. Cosmos needs-team-attention This issue needs attention from Azure service team or SDK team Service Attention This issue is responsible by Azure service team.

Comments

@FabianMeiswinkel
Copy link
Member

Is your feature request related to a problem? Please describe.
Today when a read region loses the read lease it returns 410/LeaseLost - the client will then retry locally for up-to 30 seconds (catch-all 410 retry like for 410/0 or connectivity related 410) .

Describe the solution you'd like
Instead the 4120/LeaseLost should be mapped immediately to a 503 to allow the cross-regional retry to happen as quickly as possible (it should also result in per partition mark-down when available) - retrying in the next preferred region like usual for reads is acceptable.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
n/a

Information Checklist
Kindly make sure that you have added all the following information above and checkoff the required fields otherwise we will treat the issuer as an incomplete report

  • Description Added
  • Expected solution specified
@github-actions github-actions bot added Client This issue points to a problem in the data-plane of the library. Cosmos needs-team-attention This issue needs attention from Azure service team or SDK team Service Attention This issue is responsible by Azure service team. labels Apr 4, 2024
Copy link

github-actions bot commented Apr 4, 2024

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @kushagraThapar @pjohari-ms @TheovanKraay.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Client This issue points to a problem in the data-plane of the library. Cosmos needs-team-attention This issue needs attention from Azure service team or SDK team Service Attention This issue is responsible by Azure service team.
Projects
None yet
Development

No branches or pull requests

1 participant