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

API to update node attributes dynamically #108632

Closed
namannigam opened this issue May 14, 2024 · 2 comments
Closed

API to update node attributes dynamically #108632

namannigam opened this issue May 14, 2024 · 2 comments
Labels
:Distributed/Allocation All issues relating to the decision making around placing a shard (both master logic & on the nodes) >enhancement Team:Distributed Meta label for distributed team

Comments

@namannigam
Copy link

Description

While trying our hands on an existing production cluster to perform shard-allocation-filtering.
I realized realizing that the node attributes, if added to a cluster, must be updated during a startup or a restart of each cluster node has to be performed.

Is it convenient and feasible to expose an API for settings to update node attributes and modify them dynamically? In cases, specifically when I want to associate just a label along with my nodes.

@namannigam namannigam added >enhancement needs:triage Requires assignment of a team area label labels May 14, 2024
@saikatsarkar056 saikatsarkar056 added the :Distributed/Allocation All issues relating to the decision making around placing a shard (both master logic & on the nodes) label May 14, 2024
@elasticsearchmachine elasticsearchmachine added Team:Distributed Meta label for distributed team and removed needs:triage Requires assignment of a team area label labels May 14, 2024
@elasticsearchmachine
Copy link
Collaborator

Pinging @elastic/es-distributed (Team:Distributed)

@DaveCTurner
Copy link
Contributor

Thanks for the suggestion @namannigam. It makes sense as a concept but unfortunately implementing this would be pretty tricky as things currently stand - the decision to make node attributes as they are today was made many years ago and is rather deeply embedded in the code these days. Yet, a rolling restart should not be a particularly difficult thing to do to adjust node attributes. Therefore I think it's very unlikely we'll get around to doing this for the foreseeable future so I'm going to close this issue.

@DaveCTurner DaveCTurner closed this as not planned Won't fix, can't repro, duplicate, stale May 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Distributed/Allocation All issues relating to the decision making around placing a shard (both master logic & on the nodes) >enhancement Team:Distributed Meta label for distributed team
Projects
None yet
Development

No branches or pull requests

4 participants