-
Notifications
You must be signed in to change notification settings - Fork 86
Removes per-shard ShardReplicationTask from cluster state
#1695
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
Open
jainankitk
wants to merge
7
commits into
opensearch-project:main
Choose a base branch
from
jainankitk:remove-shard-tasks
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
a5d503b
Add NodeReplicationController and ShardReplicationContext infra
jainankitk 08cdf15
Remove ShardReplicationTask and wire up NodeReplicationController
jainankitk a209f11
Add unit tests, fix integ regressions from shard-task removal
jainankitk 521067c
Fix failing integration tests
jainankitk 8770083
Merge branch 'main' into remove-shard-tasks
jainankitk dbaf1ba
Fix build failures due to missing commits
jainankitk 5e8f01b
Restore BWC stubs for legacy shard task params/state
jainankitk 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
Large diffs are not rendered by default.
Oops, something went wrong.
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.
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.
In IndexReplicationState.kt, the new FollowingState.fromStream(inp) reads inp.readVInt() to get the count of legacy shard entries, but the repeat(count) block is empty — it doesn't actually consume the bytes from the stream
If a legacy FollowingState payload is encountered during a rolling upgrade (before CleanupShardTasksUpdateTask runs), the unread bytes will corrupt the stream position and cause opaque deserialization failures downstream. The automated code analyzer already flagged this. The invoke(inp) operator also discards the stream without consuming it. Both need to actually drain the legacy bytes or the BWC story is broken.