Github user zhouxinyu commented on the issue:
Hi, @lizhanhui , what's the appearance/effect of this BUG?
Let's start from the next round.
IMO, it's ok when ConsumeQueue-MappedFile hold failed, this file will be
released by the last holder, while the empty mapped file will retain in
MappedFileQueue, but the min consume queue offset will be corrected.
It seems that the only problem is the hanged consume queue only can be
deleted when restart the broker.
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket