Aias00 opened a new issue, #7194: URL: https://github.com/apache/rocketmq-dashboard/issues/7194
### Problem On `rocketmq-studio` at `127c47b06a268cc74224d5f34c56ec7c36ac0d55`, `ResourceOwnershipGuard.withOwned` acquires the instance identity mutex and instance row lock, then holds them through `action.get()`, including remote send/reset/replay RPCs. Writes to unrelated topics of the same instance therefore serialize and keep database transactions/connections open while waiting on the network. ### Proposed Work Document and agree on a measured concurrency design before changing runtime locking. Establish a baseline with two independent resources on the same instance, define safe concurrency between resource writes and instance deletion/connection updates, and specify failure and crash behavior. The first PR is a design document for review; it does not remove ownership guards. ### Acceptance Criteria - Reproducible benchmark plan distinguishes instance-lock waits from broker latency. - Resource writes keep ownership validation and serialize conflicting operations. - Instance deletion and endpoint/credential changes cannot race admitted remote writes. - Multi-process correctness and MySQL/H2 semantics are explicitly assessed. - Alternatives and rollout gates are documented; production changes require agreement and tests. ### Related Work #4755 addresses pooled client retirement and in-flight actions, not contention in the database ownership mutex. No duplicate ownership-lock concurrency issue was found in the all-state issue/PR search. -- 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]
