[jira] [Created] (ARTEMIS-6163) Add auto-start attribute and management start/stop operations for lock coordinators

["Michael Lukyanov (Jira)" <ji...@apache.org>]

Michael Lukyanov created ARTEMIS-6163:
-----------------------------------------

             Summary: Add auto-start attribute and management start/stop operations for lock coordinators
                 Key: ARTEMIS-6163
                 URL: https://issues.apache.org/jira/browse/ARTEMIS-6163
             Project: Artemis
          Issue Type: Improvement
            Reporter: Michael Lukyanov


Follow-up to ARTEMIS-6162. Even with lock coordinators starting only on activation, all active brokers sharing a lock still race for it -
  after a primary fails, a broker in a standby DC can grab the lock before the failed primary's own backup finishes activating.

  This adds an auto-start attribute on lock-coordinator (default true, no behaviour change) and startLockCoordinator/stopLockCoordinator
  management operations. Brokers that should only take over after a human decision (e.g. a standby DC) can be configured with
  auto-start=false: the coordinator is created but never contends for the lock until started explicitly through management. Making the lock
  manager auto-start=false was suggested by Clebert on the users list ("Artemis Cluster with HA and with Mesh Mirror", May 2026).



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@artemis.apache.org
For additional commands, e-mail: issues-help@artemis.apache.org