-
Notifications
You must be signed in to change notification settings - Fork 25.2k
Add min. read-only index version compatible to DiscoveryNode #118744
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
Merged
tlrx
merged 16 commits into
elastic:main
from
tlrx:2024/12/16/add-min-readonly-index-compatible-version-to-node
Dec 17, 2024
Merged
Changes from all commits
Commits
Show all changes
16 commits
Select commit
Hold shift + click to select a range
cd9c2d3
Add min. read-only index version compatible to DiscoveryNode
tlrx 6f2c230
Merge branch 'main' into 2024/12/16/add-min-readonly-index-compatible…
tlrx 3088482
Merge branch 'main' into 2024/12/16/add-min-readonly-index-compatible…
tlrx 2b4fa25
xcontent + tests
tlrx a3f4eeb
Merge branch 'main' into 2024/12/16/add-min-readonly-index-compatible…
tlrx e768dff
fix yaml test
tlrx 80d491b
Merge branch 'main' into 2024/12/16/add-min-readonly-index-compatible…
tlrx d23319b
feedback
tlrx 1a2f9a0
Merge branch 'main' into 2024/12/16/add-min-readonly-index-compatible…
tlrx 85d604a
Merge branch 'main' into 2024/12/16/add-min-readonly-index-compatible…
tlrx 404a151
Merge branch 'main' into 2024/12/16/add-min-readonly-index-compatible…
tlrx b41f78a
Merge branch 'main' into 2024/12/16/add-min-readonly-index-compatible…
tlrx f7e8af4
Merge branch 'main' into 2024/12/16/add-min-readonly-index-compatible…
tlrx 8b1ebcd
Merge branch 'main' into 2024/12/16/add-min-readonly-index-compatible…
tlrx 72ca17a
Merge branch 'main' into 2024/12/16/add-min-readonly-index-compatible…
tlrx 042d00c
Merge branch 'main' into 2024/12/16/add-min-readonly-index-compatible…
tlrx File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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 is good, but perhaps you can confirm my thinking here. I originally worried a little about it persisting due to residing in cluster state such that it would depend on the master's version.
It should work though since we require a full upgrade to 8.18 before upgrading to 9.0 (at least in a rolling fashion). Hence on 8.18, any master here would then see a new 9.0 node, hence it would have the N-2 min-read-only-version.
All good I think, just overcomplicating it (I think).
Uh oh!
There was an error while loading. Please reload this page.
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 think it is OK too, yet it is not an area I'm super confortable with.
My understanding is that a cluster on 8.17 with indices created in 7.x should reject join requests from 9.0 nodes since the node will only communicate a min. index compatible version on 8.
Once this PR is merged in
main
and backported to 8.18, a master on 8.18 will receive join requests from 9.0 nodes with both the N-1 and N-2 information but should still reject the node if 7.x indices exist in the cluster since 9.0 is not able to read andwrite such indices (I expect to change this soon for read-only searchable snapshot indices in #118785).