-
Notifications
You must be signed in to change notification settings - Fork 25.6k
[doc] 6.8 deprecation logging bug - known issue #62869
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
Conversation
|
Pinging @elastic/es-core-infra (:Core/Infra/Logging) |
|
Pinging @elastic/es-docs (>docs) |
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.
Looks good overall. I left a comment regarding clarity.
| Deprecation Logging:: | ||
|
|
||
| In a mixed cluster environment where one of the nodes is 6.7 but coordinating node is 6.7 | ||
| an exception will be thrown when a deprecation warning is emitted on pre 6.7 node. | ||
| it was introduced by (PR: {es-pull}/37622[#37622]) in order to speed up the performance of header warning parsing. |
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.
It's not clear which node is pre-6.7.
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.
good point, it did not made sense :D thanks
Co-authored-by: James Rodewig <[email protected]>
known issue doc on a bug #60561