Github user lizhanhui commented on the issue:
> what's the appearance/effect of this BUG?
Reported bug description is consume queue files cannot be automatically
deleted and took up large portion of disk.
> 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.
ConsumeQueue#correctMinOffset will not work as expected if consume queue
file hanged. Double check the source code to figure out.
> It seems that the only problem is the hanged consume queue only can be
deleted when restart the broker.
Not only this one. As correcting min offset is also affected, consumer
client probably experiences long term of "commit log being deleted." before
consuming progress catches up. There should be additional potential issues.
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