tju-yxq opened a new pull request, #2596:
URL: https://github.com/apache/rocketmq-dashboard/pull/2596

   Closes #2595
   
   ## Summary
   
   - enrich a discovery result with one shared attempted-broker-address set
   - attempt each distinct broker address at most once per discovery call
   - let duplicate clusters referencing an unavailable broker use their 
persisted-config fallback immediately
   - preserve existing single-cluster detail enrichment behavior
   - add a regression test with two discovered clusters sharing one unavailable 
broker
   
   ## Why
   
   Each discovered cluster previously performed live broker-config enrichment 
independently. Discovery can return multiple registry views containing the same 
broker; when that broker was unavailable, every duplicate repeated the same 
failing admin call before falling back.
   
   ## Tests
   
   - focused: `ClusterServiceTest` — 39 tests passed, Checkstyle 0 violations
   - backend full suite: 1,627 tests run; only the 2 pre-existing 
`RocketMQMessageProviderTest` failures remain
   - `git diff --check`: passed
   
   Production changes: 31 additions / 3 deletions. The full PR is 64 additions 
/ 3 deletions. This is a real efficiency/fallback fix, but production changed 
lines are below the separate 100-line target, so the tracking ledger records it 
as a candidate rather than a complete group.


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