-
Notifications
You must be signed in to change notification settings - Fork 24.8k
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
Nodes types filters order not kept for _nodes API #41885
Comments
Pinging @elastic/es-distributed |
@fpompermaier for this one, I don't think you are right.
|
Also, when putting |
Actually I'm trying the following requests on http://demo.elastic.co/app/kibana (7.0.0) but the documented statements are not true.. GET _nodes/_all # OK, returns all 9 nodes Am I wrong @astefan ? |
@fpompermaier you are right and we might have a bug in our code. Looking into it. And I'm re-opening this issue. Thank you for your diligence on this issue. |
In the cluster API the following NOTE is wrong (I think):
node filters run in the order in which they are given, which is important if using filters that remove nodes from the set. For example _all,master:false means all the nodes except the master-eligible ones, but master:false,_all means the same as _all because the _all filter runs after the master:false filter.
It should be:
node filters run in the order in which they are given, which is important if using filters that remove nodes from the set. For example _all,master:false means all the nodes except the master-eligible ones, but master:false,_all means the same as master:false because the _all filter runs after the master:false filter.
The text was updated successfully, but these errors were encountered: