-
Notifications
You must be signed in to change notification settings - Fork 25.6k
Change token for nodes stats adaptive selection submetric #54193
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
Change token for nodes stats adaptive selection submetric #54193
Conversation
|
Pinging @elastic/es-core-infra (:Core/Infra/Plugins) |
bpintea
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
| DISCOVERY("discovery"), | ||
| INGEST("ingest"), | ||
| ADAPTIVE_SELECTION("adaptiveSelection"); | ||
| ADAPTIVE_SELECTION("adaptive_selection"); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure changing this will work in 7.x, because in mixed cluster, the server/request would not align? Additionally, the transport client would have similar failure scenarios?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My plan is that this PR will change the token in 7.7, which will mean that 7.7.0 and all following 7.7.x releases will have the change. #53637 will make the change in master and the change will come in for 7.x in #54141. Both of those PRs are ready for merge once this issue is resolved. I believe that if we make this change on 7.7, 7.x, and master, then there won't be any releases where the versions won't align. Does that make sense? Am I missing something?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the explanation. I just realized where my confusion lies: I was thinking this enum existed and these strings were serialized currently, when in fact the 7.6 and before request is serialized with boolean flags.
rjernst
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
| DISCOVERY("discovery"), | ||
| INGEST("ingest"), | ||
| ADAPTIVE_SELECTION("adaptiveSelection"); | ||
| ADAPTIVE_SELECTION("adaptive_selection"); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the explanation. I just realized where my confusion lies: I was thinking this enum existed and these strings were serialized currently, when in fact the 7.6 and before request is serialized with boolean flags.
This is a small bit of #53637 that will save us some headaches if it sneaks into 7.7 before we cut an official release. It just changes the value of a string constant that is being introduced in 7.7.
As described here, this is not a change to the user-facing value for the adaptive selection metric. It simply changes the internal token so that it matches the adaptive selection metric.