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.
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
Add target search concurrency to TieredMergePolicy #13430
Add target search concurrency to TieredMergePolicy #13430
Changes from 6 commits
ab0a13a
ecf2035
6bf94d2
36ad550
585c927
c922f47
f74616c
31e132f
2d6173d
22436c0
7c4397e
289d07d
d4d89f1
bfdb58b
f240644
500fe32
1b91298
299ac18
e058a9f
9ab6fcd
d44de4c
66d62e9
ca4c19c
2c18e5f
1b9b60b
3db835a
2d80315
8de0212
898e2e8
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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 don't think that we want to do this.
hitTooLarge
is considered a good thing by this merge policy. It means that we found a merge that reached the maximum merged segment size. It's great because if we perform this merge, then this segment will not be eligible again for merging (unless it gets many deletes), so we'll essentially be done with it. So these merges are given a very good score by assuming that they have a perfect skew.hitMaxDocs
is different, we don't want to prioritize unbalanced merges that produce segments ofhitMaxDocs
documents? It's better to keep prioritizing balanced small segment merges as usual?My expectation for handling
allowedMaxDoc
is that we would just never score any merge that has more thanallowedMaxDoc
documents and force the merge policy to select one of the candidate merges that produce fewer documents than that.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 see - I was thinking in doing the same with docs than with bytes, but I see they're quite different. Docs is more a hint to maintain the number of segments we want, but bytes provides a hard limit on size and also score guidance on segments to merge.