-
Notifications
You must be signed in to change notification settings - Fork 11.6k
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
There may be a bug in DefaultMessageStore#getMessage #5162
Comments
For some pulled messages for maxMsgNums could be filter-out. so
but it seems need some updates on if ((cqUnit.getQueueOffset() - offset) * CQ_STORE_UNIT_SIZE > maxFilterMessageCount) {
break;
} |
IMO you're right. |
ok. I will submit a PR to fix this later on. |
LGTM~ |
… calculating (#5171) * fix bug for comparing size with count * add getUnitSize function
… calculating (#5171) * fix bug for comparing size with count * add getUnitSize function
maxFilterMessageCount
is calculated asmaxMsgNums * ConsumeQueue.CQ_STORE_UNIT_SIZE
and it's seems like meaning the maxFilterMessageSize.and it's used to judge wether this pull has scanned enough message as follow
the cqUnit.queueOffset is logic offset of consumer queue which is calculated as follow
Is there something going wrong? or if I made some mistake when reading source code and submitting issue, please figure it out thanks
The text was updated successfully, but these errors were encountered: