You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@rocketmq.apache.org by GitBox <gi...@apache.org> on 2026/10/20 19:50:53 UTC
[GH] (rocketmq-dashboard/fix/btl-litetopic-ttl): Workflow run "CI" is working again!
The GitHub Actions job "CI" on rocketmq-dashboard.git/fix/btl-litetopic-ttl has succeeded.
Run started by GitHub user btlqql (triggered by btlqql).
Head commit for run:
018ffb0c9962e91d882a985aec5d33262b30e6dc / btlqql <29...@qq.com>
fix(litetopic): report partial multi-master TTL updates instead of a bare write error (#7085)
extendTTL writes lite.topic.expiration to every broker master that carries the Lite parent
topic. When a later write failed, the earlier masters kept the new expiration but the caller
only received the raw write error, so a cluster could stay split between the old and the new
TTL with nothing in the response saying which masters had been changed.
The write phase now tracks the masters it already updated and, on a failure after the first
one, throws a 502 BusinessException that names the updated masters, the failed master with its
error and the masters that were not attempted, plus the recovery path: the extension is
idempotent, so re-running it converges every master. A failure on the first write still
propagates unchanged and the all-master success path is untouched.
Report URL: https://github.com/apache/rocketmq-dashboard/actions/runs/39459184979
With regards,
GitHub Actions via GitBox