yx9o opened a new issue, #11486: URL: https://github.com/apache/rocketmq/issues/11486
### Before Creating the Bug Report - [x] I found a bug, not just asking a question, which should be created in [GitHub Discussions](https://github.com/apache/rocketmq/discussions). - [x] 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. - [x] I have confirmed that this bug belongs to the current repository, not other repositories of RocketMQ. ### Runtime platform environment macOS 13.5.2 (unit tests). ### RocketMQ version develop, commit 38a7ca0d23a3e2d4339f9a2bf6e78cf541eed9e3. ### JDK Version Oracle JDK 22.0.2. ### Describe the Bug In Exclusive mode, a stale full subscription sync re-adds an evicted LiteTopic client to the dispatch index despite its eviction tombstone, potentially stalling consumption. ### Steps to Reproduce 1. Client A subscribes to a LiteTopic in an Exclusive group. 2. Client B subscribes to the same LiteTopic and evicts A. 3. A sends a full subscription sync still containing that LiteTopic. ### What Did You Expect to See? Only B remains subscribed; A must explicitly re-subscribe to reclaim ownership. ### What Did You See Instead? A is re-added alongside B; events dispatched to A are discarded by the POP tombstone check. ### Additional Context Confirmed by a regression test that fails before the fix; all 100 related registry, dispatcher and POP tests pass after the fix. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
