apache / apache/rocketmq-dashboard
Add NameServer registry reconciliation report
- Dominant language
- Java
- Stars
- 1.4k
- Forks
- 683
- Avg merge
- 2d 14h
- Merged PRs (30d)
- 58
Description
## Problem
The cluster page exposes both persisted NameServer registry entries and clusters discovered from the selected RocketMQ instance, but operators must reconcile these views manually. Stale entries, missing registrations, ambiguous matches, duplicate mappings, and address drift can therefore remain hidden.
## Proposed change
Add a read-only reconciliation drawer that:
- normalizes multi-address values before comparison;
- correlates registry entries and discovered clusters by name or address;
- reports matched, address-mismatch, registry-only, discovery-only, ambiguous, and duplicate mappings;
- shows configured, discovered, missing, and unexpected addresses;
- supports attention filtering and search;
- includes focused deterministic tests and Chinese/English copy.
The implementation reuses data already loaded by the cluster page and performs no registry mutations or extra network probes.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start at the cluster page and trace the already loaded persisted registry entries and discovered clusters. Define deterministic cases for matching, mismatches, missing and duplicate mappings, then verify the read-only drawer's attention filter, search, address display, and Chinese/English copy. Done means the reconciliation report uses no mutations or extra network probes and its focused tests pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- frontend, internationalization, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100