[fix][ml] PIP-430: Fix concurrency issue in MessageMetadata caching and improve caching #24836
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.
Fix #24831
Motivation
The test ManagedCursorConcurrencyTest.testConcurrentReadOfSameEntry is flaky. In that case, the entries don't contain any message metadata. The broker cache will attempt to parse the message metadata each time the entry is cached. This results in a race condition since peekMessageMetadata changes the readerIndex of the cached ByteBuf while another thread is making a retained duplicate of the cached ByteBuf. Thanks for @pdolif for the analysis of the problem. It was helpful in locating the issue.
Modifications
Documentation
docdoc-requireddoc-not-neededdoc-complete