RockteMQ-AI commented on issue #4333: URL: https://github.com/apache/rocketmq-dashboard/issues/4333#issuecomment-5680641870
**Issue Evaluation** Category: `enhancement` | Status: **Evaluated** **Feasibility:** Feasible but complex **Scope:** Dashboard backend (new service + controller) + frontend (new modal) **Compatibility:** No breaking changes — additive feature Message deduplication and idempotency health monitoring is a meaningful operational feature, especially for financial and order-processing workloads where duplicate delivery has business impact. **Assessment:** - The use case is valid — producer retries and network duplications are common in distributed messaging - The proposed `TopicDeduplicationHealthReport` model covers the right dimensions (duplication ratio, delta distribution, idempotency gap analysis) - **Complexity consideration:** Calculating duplication ratios at scale requires sampling or approximate algorithms (e.g., HyperLogLog for cardinality estimation). Exact deduplication analysis on high-throughput topics would be prohibitively expensive - The business key duplicati on detection should be configurable per topic, as not all topics use business keys - Consider: integration with RocketMQ's existing message trace feature could provide the raw data for deduplication analysis without additional broker-side instrumentation This feature would be most impactful when combined with the message trace module. --- *Automated evaluation by github-manager-bot* -- 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]
