RockteMQ-AI commented on issue #10541: URL: https://github.com/apache/rocketmq/issues/10541#issuecomment-4782071399
**Issue Evaluation** Category: `type/bug` | Status: **Confirmed** The repeated "subscription changed" logging has been verified against the current codebase. **Root Cause:** In `ConsumerGroupInfo#updateSubscription()` (broker module), the comparison `sub.getSubVersion() > old.getSubVersion()` is always true for gRPC clients because each heartbeat creates a new `SubscriptionData` via `FilterAPI.build()` → `new SubscriptionData()` which sets `subVersion = System.currentTimeMillis()`. The actual subscription content (topic, expression, tags) is never compared — only the timestamp-based version. Additionally, the `subscriptionTable.put()` in this branch does not set `updated = true`, so the method returns false even though the table was modified, creating an inconsistent state. **Impact:** Excessive INFO-level logging in production environments with gRPC consumers, making it harder to identify genuine subscription changes. **Severity:** Medium — affects observability and log storage, not message delivery. An automated fix proposal will be generated. Reply `/approve` to proceed with PR generation. --- *Automated evaluation by RockteMQ-AI* -- 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]
