[Test] Tests sequence number pruning after merge for standard indices#143690
Merged
tlrx merged 16 commits intoelastic:mainfrom Mar 9, 2026
Merged
[Test] Tests sequence number pruning after merge for standard indices#143690tlrx merged 16 commits intoelastic:mainfrom
tlrx merged 16 commits intoelastic:mainfrom
Conversation
19 tasks
Collaborator
|
Pinging @elastic/es-distributed (Team:Distributed) |
fcofdez
approved these changes
Mar 6, 2026
| ); | ||
|
|
||
| // waits for retention leases to advance past all docs | ||
| assertBusy(() -> { |
Contributor
There was a problem hiding this comment.
Maybe we need to add a test where we create a retention lease to ensure that we do not remove sequence numbers from the retention lease seq_no onwards? It could be in a follow up 👍
Member
Author
There was a problem hiding this comment.
Makes perfect sense, I'll do it in a follow up.
tlrx
added a commit
to tlrx/elasticsearch
that referenced
this pull request
Mar 9, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This commit adds an integration test for checking that sequence number are correctly pruned after segments are merged (in the test, force-merged) and triggers a peer-recovery afterwards.
Relates #143583