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
Cluster state does not always contain correct node roles #71385
Labels
>bug
:Distributed/Cluster Coordination
Cluster formation and cluster state publication, including cluster membership and fault detection.
Team:Distributed
Meta label for distributed team
Comments
DaveCTurner
added
>bug
:Distributed/Cluster Coordination
Cluster formation and cluster state publication, including cluster membership and fault detection.
labels
Apr 7, 2021
Pinging @elastic/es-distributed (Team:Distributed) |
DaveCTurner
added a commit
to DaveCTurner/elasticsearch
that referenced
this issue
Apr 7, 2021
Today the response to `GET _cluster/state` does not include the roles of the nodes in the cluster. In the past this made sense, roles were relatively unchanging things that could be determined from elsewhere. These days we have an increasingly rich collection of roles, with nontrivial BWC implications, so it is important for debugging to be able to see the specific roles as viewed by the master. This commit adds the role names to the cluster state API output. Relates elastic#71385
DaveCTurner
added a commit
that referenced
this issue
Apr 7, 2021
Today the response to `GET _cluster/state` does not include the roles of the nodes in the cluster. In the past this made sense, roles were relatively unchanging things that could be determined from elsewhere. These days we have an increasingly rich collection of roles, with nontrivial BWC implications, so it is important for debugging to be able to see the specific roles as viewed by the master. This commit adds the role names to the cluster state API output. Relates #71385
DaveCTurner
added a commit
to DaveCTurner/elasticsearch
that referenced
this issue
Apr 7, 2021
Today the response to `GET _cluster/state` does not include the roles of the nodes in the cluster. In the past this made sense, roles were relatively unchanging things that could be determined from elsewhere. These days we have an increasingly rich collection of roles, with nontrivial BWC implications, so it is important for debugging to be able to see the specific roles as viewed by the master. This commit adds the role names to the cluster state API output. Relates elastic#71385
DaveCTurner
added a commit
to DaveCTurner/elasticsearch
that referenced
this issue
Apr 7, 2021
Today the response to `GET _cluster/state` does not include the roles of the nodes in the cluster. In the past this made sense, roles were relatively unchanging things that could be determined from elsewhere. These days we have an increasingly rich collection of roles, with nontrivial BWC implications, so it is important for debugging to be able to see the specific roles as viewed by the master. This commit adds the role names to the cluster state API output. Relates elastic#71385 Backport of elastic#71386
DaveCTurner
added a commit
that referenced
this issue
Apr 7, 2021
Today the response to `GET _cluster/state` does not include the roles of the nodes in the cluster. In the past this made sense, roles were relatively unchanging things that could be determined from elsewhere. These days we have an increasingly rich collection of roles, with nontrivial BWC implications, so it is important for debugging to be able to see the specific roles as viewed by the master. This commit adds the role names to the cluster state API output. Relates #71385 Backport of #71386
This only affects upgrades from versions that are now long-past EOL, so I'm closing it. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
>bug
:Distributed/Cluster Coordination
Cluster formation and cluster state publication, including cluster membership and fault detection.
Team:Distributed
Meta label for distributed team
Elasticsearch version (
bin/elasticsearch --version
): 7.11.1, likely othersPlugins installed:
[]
JVM version (
java -version
): BundledOS version (
uname -a
if on a Unix-like system):CentOS Linux 7 (Core) 3.10.0-693.21.1.el7.x86_64
Description of the problem including expected versus actual behavior:
A cluster that was fully upgraded to a data-tiers-based 7.11.1 was seen to still have nodes with the
data
role in the cluster state:There should be no
d
nodes in this cluster any more.Steps to reproduce:
Unknown at the moment, this is exactly what #64693 is supposed to address.
The text was updated successfully, but these errors were encountered: