Use HashMap for IndexMetadata.inSyncAllocationIds#86403
Merged
rjernst merged 4 commits intoelastic:masterfrom May 4, 2022
Merged
Use HashMap for IndexMetadata.inSyncAllocationIds#86403rjernst merged 4 commits intoelastic:masterfrom
rjernst merged 4 commits intoelastic:masterfrom
Conversation
The in sync allocation ids is a mapping from shard to the set of ids currently being processed. When being built, the metadata uses a sparse map, only filling a value for a shard as they are put into the builder. When the final metadata is built, the map is made dense. This commit converts to using a HashMap instead of ImmutableOpenIntMap. The boxed keys should not cause allocations, as long as number of shards is lower than 128. Long term the map itself should become an array, as we know the number of shards (much like the dense primaryTerms array here). However, that change will be a little trickier to make, since we will need to be backward compatible with how diffs are built, currently using Map differences. relates elastic#86239
Collaborator
|
Pinging @elastic/es-distributed (Team:Distributed) |
35 tasks
original-brownbear
approved these changes
May 4, 2022
Contributor
original-brownbear
left a comment
There was a problem hiding this comment.
LGTM. I'll try not to forget the follow up to move this to an array :)
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
3 participants
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.
The in sync allocation ids is a mapping from shard to the set of ids
currently being processed. When being built, the metadata uses a sparse
map, only filling a value for a shard as they are put into the builder.
When the final metadata is built, the map is made dense.
This commit converts to using a HashMap instead of ImmutableOpenIntMap.
The boxed keys should not cause allocations, as long as number of shards
is lower than 128. Long term the map itself should become an array, as
we know the number of shards (much like the dense primaryTerms array
here). However, that change will be a little trickier to make, since we
will need to be backward compatible with how diffs are built, currently
using Map differences.
relates #86239