yuluo-yx opened a new issue, #3071:
URL: https://github.com/apache/rocketmq-dashboard/issues/3071

   ## Problem
   
   Operators that manage the same logical topics in multiple RocketMQ instances 
currently have to open each instance separately and compare its Topic settings 
by hand. The Topic list also contains runtime counters and timestamps, so a raw 
row comparison produces noise and can hide configuration drift that changes 
routing or write behavior.
   
   This is especially error-prone before a migration, disaster-recovery 
exercise, or production rollout, where queue counts, permissions, topic type, 
or namespace may differ between clusters.
   
   ## Proposed solution
   
   Add a read-only cross-instance Topic configuration comparison workflow to 
the Studio Topic page:
   
   - select a source and target instance, with a one-click swap action;
   - load the complete paginated Topic inventory from both instances;
   - compare only stable configuration fields: topic type, namespace, read 
queues, write queues, and permissions;
   - classify rows as matching, drifted, source-only, or target-only;
   - filter and search the comparison, expand a row to inspect field-level 
differences, and export the filtered result as CSV;
   - keep runtime counters, message volume, TPS, timestamps, and 
instance-specific identifiers out of the comparison.
   
   The workflow must remain read-only and must not copy or mutate Topic 
configuration.
   
   ## Acceptance criteria
   
   - [ ] Comparison is available only when at least two instances are 
configured.
   - [ ] All pages of each selected instance are included.
   - [ ] Results are deterministic and distinguish match, drift, source-only, 
and target-only states.
   - [ ] Drift details identify each differing stable configuration field and 
both values.
   - [ ] Search, status filtering, swapping, and CSV export work without 
mutating a Topic.
   - [ ] Stale asynchronous responses cannot replace the latest comparison.
   - [ ] Unit and component tests cover matching, each stable field, ignored 
runtime data, missing topics, filters, CSV export, loading failures, and 
insufficient instances.
   
   ## Duplicate check
   
   Searched open and closed issues and pull requests for `cross-instance topic 
comparison`, `topic configuration drift`, `compare topic configuration`, and 
`topic config comparison`. Existing configuration-drift work is for 
NameServer/Broker nodes and does not provide Topic inventory comparison.
   


-- 
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]

Reply via email to