RockteMQ-AI commented on issue #11041: URL: https://github.com/apache/rocketmq/issues/11041#issuecomment-5552036478
**Issue Evaluation** Category: `bug` | Status: **Confirmed** The off-by-one error in paginated metadata sync is verified against the current codebase: - `MQClientAPIImpl.java:3125` — `topicSeq >= totalTopicNum - 1` (should be `>= totalTopicNum`) - `MQClientAPIImpl.java:3033` — `groupSeq >= totalGroupNum - 1` (same) - `BrokerOuterAPI.java:834` / `984` — identical pattern, affects slave sync via `SlaveSynchronize#syncTopicConfig` When topic/group count N ≡ 1 (mod pageSize), the last entry is silently dropped. The `DataVersion` comparison then matches, so no resync occurs — the missing entry persists indefinitely. **Severity:** Medium-High — silent data loss for exactly one topic/group per page boundary; slave brokers permanently miss the last topic **Impact:** Client metadata sync, master-slave replication Fix PR #11042 correctly changes the termination condition to `seq >= totalNum`. --- *Automated evaluation by github-manager* -- 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]
