[WIP] fix memory leak: Use ConcurrentLongLongPairHas that supports to shrink #14407
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.
Motivation
issue: #14268
Using the latest version in bookkeeper, the ConcurrentLongLongPairHashMap of this version supports to shrink when removing, which can solve the problem of continuous memory increase and frequent FGC in pulsar broker.
See the PR corresponding to bookkeeper: apache/bookkeeper#3061.
I need to wait for bookkeeper to release a new version, then I will change the version that bookkeeper depends on in pom.
Documentation
Check the box below or label this PR directly (if you have committer privilege).
Need to update docs?
doc-required
(If you need help on updating docs, create a doc issue)
no-need-doc
(Please explain why)
doc
(If this PR contains doc changes)