Aias00 opened a new pull request, #7196:
URL: https://github.com/apache/rocketmq-dashboard/pull/7196

   ### Related Issue
   
   Refs #7194.
   
   ### Brief Description
   
   Ownership guards currently hold an exclusive instance mutex and row lock 
through remote resource writes. Unrelated topics in one instance therefore 
contend on the same admission lock and occupy database connections while 
waiting on remote actions.
   
   Add a design proposal that defines the invariants, deterministic contention 
experiment, two-process/MySQL verification, and alternatives to evaluate before 
changing runtime behavior. Assess shared instance admission versus durable 
reservations, including virtual-instance registration, lock ordering, recovery, 
and remote fencing limitations.
   
   This PR is intentionally a draft for design review, following 
CONTRIBUTING.md's requirement to discuss non-trivial designs before 
implementation. It changes documentation only. It does not claim benchmark 
results or solve the runtime contention yet; the issue stays open for 
measurement and agreement.
   
   ### How Did You Test This Change?
   
   - Reviewed the proposal against ResourceOwnershipGuard.withOwned, write, 
lockInstance, lockIdentity, and instance update/deletion/registration paths at 
upstream 127c47b06a268cc74224d5f34c56ec7c36ac0d55.
   - `git diff --cached --check`: passed.
   - Documentation only; no runtime tests or benchmarks were executed for this 
proposal.
   
   ### Checklist
   
   - [x] One coherent documentation change
   - [x] Conventional commit subject
   - [x] No runtime, schema, dependency, or UI changes
   - [x] Required safety properties, alternatives, and rollout gates documented
   - [ ] Maintainer agreement on the coordination design
   


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