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] [Remote store] Throttling from remote store shouldn't cause leader stepping down and re-elections #10683

Open
shwetathareja opened this issue Oct 18, 2023 · 2 comments

Comments

@shwetathareja
Copy link
Member

Describe the bug

With the remote storage, leader writes the cluster state to both local and remote storage. At times, when the remote storage is experiencing surge in traffic, it can start throttling the requests. This can cause state upload to fail and would cause leader to step down and would result in re-elections. This can go in a loop until throttling subsides.

Expected behavior
Enhance the exception handling where leader need not step down for cases where cluster state updates are failing purely due to remote store throttling.

@shwetathareja shwetathareja added bug Something isn't working untriaged Cluster Manager v2.12.0 Issues and PRs related to version 2.12.0 Storage:Remote and removed untriaged labels Oct 18, 2023
@linuxpi linuxpi added the Storage Issues and PRs relating to data and metadata storage label Oct 30, 2023
@kiranprakash154
Copy link
Contributor

Hi, are we on track for this to be released in 2.12 ?

@soosinha
Copy link
Member

soosinha commented Mar 8, 2024

Removing the 2.12 tag. This will be picked up later

@Bukhtawar Bukhtawar added ClusterManager:RemoteState and removed Storage Issues and PRs relating to data and metadata storage Storage:Remote labels May 16, 2024
@rwali-aws rwali-aws moved this from 🆕 New to Next (Next Quarter) in Cluster Manager Project Board Jun 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Next (Next Quarter)
Development

No branches or pull requests

5 participants