[Bug] Clean MemoryConsumerOrderInfo if group does not exist

[imzs]

Before Creating the Bug Report

• I found a bug, not just asking a question, which should be created in GitHub Discussions.

• I have searched the GitHub Issues and GitHub Discussions of this repository and believe that this is not a duplicate.

• I have confirmed that this bug belongs to the current repository, not other repositories of RocketMQ.

Runtime platform environment

RocketMQ version

JDK Version

Describe the Bug

MemoryConsumerOrderInfoManager, as an internal manager, lacks external autoClean invocation and cannot perform fallback cleanup when the group is missing.

Steps to Reproduce

.

What Did You Expect to See?

Execute autoClean periodically.

What Did You See Instead?

.

Additional Context

.

[salmaloel657-dotcom]

Describe the Bug MemoryConsumerOrderInfoManager doesn’t have any external trigger for autoClean, so it can’t clean up properly when a consumer group is missing. What Did You Expect to See? autoClean being executed periodically to handle stale or missing groups. What Did You See Instead? No cleanup happens in those cases.

…

On Fri, Apr 3, 2026, 5:01 AM imzs ***@***.***> wrote: *imzs* created an issue (apache/rocketmq#10244) <#10244> Before Creating the Bug Report - I found a bug, not just asking a question, which should be created in GitHub Discussions <https://github.com/apache/rocketmq/discussions>. - I have searched the GitHub Issues <https://github.com/apache/rocketmq/issues> and GitHub Discussions <https://github.com/apache/rocketmq/discussions> of this repository and believe that this is not a duplicate. - I have confirmed that this bug belongs to the current repository, not other repositories of RocketMQ. Runtime platform environment - RocketMQ version - JDK Version - Describe the Bug MemoryConsumerOrderInfoManager, as an internal manager, lacks external autoClean invocation and cannot perform fallback cleanup when the group is missing. Steps to Reproduce . What Did You Expect to See? Execute autoClean periodically. What Did You See Instead? . Additional Context . — Reply to this email directly, view it on GitHub <#10244?email_source=notifications&email_token=CABFFMLZDWLI3J43S7V2T734T6DWZA5CNFSL4Z3JMQ5C6L3HNF2C22DVMIXUS43TOVSS6NBRHE4TOMBWGQ2TLJTSMVQXG33OVJZXKYTTMNZGSYTFMSSWK5TFNZ2KYZTPN52GK4S7MNWGSY3L>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/CABFFMOIKRNXXMVJ73IHYCD4T6DWZAVCNFSM6AAAAACXLUQP62VHI2DSMVQWIX3LMV43ASLTON2WKOZUGE4TSNZQGY2DKNI> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>