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
[fix][broker]Fix chunked messages will be filtered by duplicating #20948
[fix][broker]Fix chunked messages will be filtered by duplicating #20948
Changes from all commits
52ae60f
30c9430
02d7071
d99ed6d
be88b7b
1c8eec3
ab69604
3be7bf0
2b05a5c
87a2513
7af1053
c4ef26f
fb1a55c
d9af22f
8655723
d7f9290
f282ac0
1f8263d
4f789ee
86c3f77
2aaac45
8579c37
3e2267c
7c813e9
233c5cc
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.
Should we handle
chunkedMsgCtx == null
in a separated block?There are actually two cases (assuming the message is split into 2 chunks):
chunkedMsgCtx
is null.chunkedMsgCtx
is not null andmsgMetadata.getChunkId() <= chunkedMsgCtx.lastChunkedMessageId
.The 1st case should be an unexpected case because message disordering happens. The 2nd case might be expected (I'm not sure) so that consumer should filter duplicated messages.
/cc @liangyepianzhou @poorbarcode
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.
There is another case:
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.
The case of
chunkedMsgCtx == null
:Case 1:
Case 2:
Case 3:
I caught
chunkedMsgCtx == null
withmsgMetadata.getChunkId() <= chunkedMsgCtx.lastChunkedMessageId
when encounter Case 3.However, after reminders and deliberation, I think these three cases can all be processed by the original logic.
/cc @BewareMyPower @poorbarcode
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.
This PR does not deduplicate the chunks in a single chunk message on the broker side.
So, the 2nd case is expected. The proposal 295 is add a patch to do deduplication of chunks on the broker side. After that the 2nd case should be an unexpected case.