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

[Remote State] Add jitter to downloads from remote store #15397

Open
soosinha opened this issue Aug 24, 2024 · 2 comments · May be fixed by #15978
Open

[Remote State] Add jitter to downloads from remote store #15397

soosinha opened this issue Aug 24, 2024 · 2 comments · May be fixed by #15978
Assignees
Labels
Cluster Manager ClusterManager:RemoteState enhancement Enhancement or improvement to existing feature or request v2.18.0 Issues and PRs related to version 2.18.0

Comments

@soosinha
Copy link
Member

Is your feature request related to a problem? Please describe

For remote cluster state publication, all the entity metadata in the cluster state are uploaded as separate files. If there are multiple entities in the cluster state that are changed, all these will be uploaded by the active cluster manager and downloaded at the same time by the follower nodes. This sudden burst in traffic to backing remote storage could cause throttling.

Describe the solution you'd like

Add jitter while downloading remote state files to mitigate the risk of throttling.

Related component

Cluster Manager

Describe alternatives you've considered

No response

Additional context

No response

@rajiv-kv
Copy link
Contributor

[Triage - attendees 1 2 3] - @soosinha is this tracked for 2.18 ?

@soosinha
Copy link
Member Author

is this tracked for 2.18 ?

Yes @rajiv-kv

Assigning to @Arpit-Bandejiya

@rwali-aws rwali-aws added v2.18.0 Issues and PRs related to version 2.18.0 and removed untriaged labels Sep 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Cluster Manager ClusterManager:RemoteState enhancement Enhancement or improvement to existing feature or request v2.18.0 Issues and PRs related to version 2.18.0
Projects
Status: Next (Next Quarter)
Development

Successfully merging a pull request may close this issue.

4 participants