You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@rocketmq.apache.org by "tju-yxq (via GitHub)" <gi...@apache.org> on 2026/09/04 16:49:47 UTC
[I] DLQ resend results do not identify failed messages [rocketmq-dashboard]
tju-yxq opened a new issue, #3161:
URL: https://github.com/apache/rocketmq-dashboard/issues/3161
## Problem
DLQ resend endpoints currently report only aggregate counts. `DLQResendResultVO` contains `matched`, `resent`, `failed`, `outcome`, `scanIncomplete`, and `failedQueueCount`, but no per-message failure information.
When a resend returns `PARTIAL` or `FAILED`, the operator still has to find the failed message IDs manually. The current response cannot answer the first questions asked during an incident:
- which dead-letter messages were not sent?
- which target topic did each failed resend use?
- why did the individual resend fail (missing target topic, producer send failure, or no resolvable destination)?
- were failures omitted from the response because a very large batch exceeded a display limit?
The selected-message resend path has the same limitation: if one of the selected messages fails, only `failed=1` is returned.
## Expected behavior
- Each failed resend should report a bounded failure entry containing the dead-letter `msgId`, resolved target topic, and a concise reason.
- Both time-range resend and selected-message resend should return the same failure-detail structure.
- The failure list should be capped (for example 100 entries) and expose whether additional failures were omitted.
- Existing aggregate fields and outcome classification should remain unchanged.
- The frontend should show the failed message IDs and reasons for `PARTIAL`/`FAILED` results so operators can retry or inspect the affected messages immediately.
--
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: commits-unsubscribe@rocketmq.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] DLQ resend results do not identify failed messages [rocketmq-dashboard]
Posted by "lizhimins (via GitHub)" <gi...@apache.org>.
lizhimins closed issue #3161: DLQ resend results do not identify failed messages
URL: https://github.com/apache/rocketmq-dashboard/issues/3161
--
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: commits-unsubscribe@rocketmq.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] DLQ resend results do not identify failed messages [rocketmq-dashboard]
Posted by "RockteMQ-AI (via GitHub)" <gi...@apache.org>.
RockteMQ-AI commented on issue #3161:
URL: https://github.com/apache/rocketmq-dashboard/issues/3161#issuecomment-5543998310
**Issue Evaluation**
Category: `enhancement` | Status: **Evaluated**
**Feasibility:** feasible
**Scope:** DLQ resend endpoints (`DLQResendResultVO`), frontend DLQ result display
**Compatibility:** backward compatible (additive change)
The request is well-scoped and addresses a real operational gap. Adding bounded per-message failure details (msgId, target topic, reason) to both time-range and selected-message resend paths is straightforward. The cap (e.g., 100 entries) with truncation disclosure is a sensible design.
**Assessment:** This enhancement improves incident response efficiency by eliminating manual failure investigation. The proposed structure preserves existing aggregate fields while adding actionable detail.
---
*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: commits-unsubscribe@rocketmq.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] DLQ resend results do not identify failed messages [rocketmq-dashboard]
Posted by "beautyarbutin (via GitHub)" <gi...@apache.org>.
beautyarbutin commented on issue #3161:
URL: https://github.com/apache/rocketmq-dashboard/issues/3161#issuecomment-5762980987
I would like to take this issue on the current `rocketmq-studio` branch. The earlier implementation in #3162 was closed without merge during the branch migration, and the failure details are still absent today. I will reimplement the behavior against the latest code, credit the prior work, preserve the existing aggregate semantics, bound and sanitize per-message failure details, and add focused backend and frontend regression coverage.
--
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: commits-unsubscribe@rocketmq.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] DLQ resend results do not identify failed messages [rocketmq-dashboard]
Posted by "lizhimins (via GitHub)" <gi...@apache.org>.
lizhimins commented on issue #3161:
URL: https://github.com/apache/rocketmq-dashboard/issues/3161#issuecomment-5806610806
Fixed in 856b97fd7 (#4817) on the `rocketmq-studio` branch.
Both DLQ resend paths (by time range and by selected message ids) now report bounded per-message failure details: each failed resend carries its DLQ `msgId`, the resolved `targetTopic` and a concise normalised `reason`. The aggregate fields are unchanged, the details are capped at 100 entries with a `failuresTruncated` flag, and the DLQ page renders the same structured details. `DLQResendResult` / `DLQResendFailure` are documented in `docs/api-spec.md` §9.2 (§9.4 returns the same shape).
Closing manually: GitHub only auto-closes an issue when the pull request is merged into the repository's default branch, and `rocketmq-studio` is not it.
--
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: commits-unsubscribe@rocketmq.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org