unbridled-41 opened a new issue, #3990:
URL: https://github.com/apache/rocketmq-dashboard/issues/3990
1. Please describe the feature you are requesting.
The consumer group settings editor (`GET/POST /api/groups/{name}/settings`,
introduced by #2512) exposes only `retryQueueNums` and `retryMaxTimes`. The
broker `SubscriptionGroupConfig` also carries the consumption switches that
operators routinely need:
- `consumeEnable` — pause/resume consumption for a group without deleting it;
- `consumeMessageOrderly` — switch a group between concurrent and orderly
consumption;
- `consumeBroadcastEnable` — allow broadcast-mode subscribers.
The classic dashboard (the previous generation in this repository,
`frontend-new/src/components/consumer/ConsumerConfigItem.jsx` on the `master`
branch) edits all of these fields via `/consumer/createOrUpdate.do`. In Studio
today they can only be changed with external tooling such as `mqadmin
updateSubGroup`.
2. Provide any additional detail on your proposed use case for this feature.
During an incident an operator needs to stop a misbehaving group from
consuming further (disable `consumeEnable`), or flip a group to orderly
consumption after introducing ordered delivery, directly from the dashboard.
The existing settings endpoint already reads the effective broker config,
updates every master broker, preserves unrelated fields, and writes an audit
record; extending it with the three switches keeps that exact contract.
Cloud instances remain unsupported for this editor, matching the current
`requireApacheInstance` scope of the settings endpoints. Omitted fields in the
update payload should preserve the current broker values.
3. Indicate the importance of this issue to you (blocker, must-have,
should-have, nice-to-have).
should-have. Workaround today is running `mqadmin updateSubGroup` manually
against every broker.
--
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]
