[
https://issues.apache.org/jira/browse/ARTEMIS-5852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18055294#comment-18055294
]
ASF subversion and git services commented on ARTEMIS-5852:
----------------------------------------------------------
Commit 4cfaadc11375cfc02eccd0e8f5b975ac00c81a5c in artemis's branch
refs/heads/main from Clebert Suconic
[ https://gitbox.apache.org/repos/asf?p=artemis.git;h=4cfaadc113 ]
ARTEMIS-5852 Lock coordination for acceptors
I'm adding a LockCoordinator to the broker, that will use DistributedLock
to help start and stop acceptors.
You can associate the LockCoordinator with acceptors and an acceptor
serving only clients would then be activated in only one of the brokers.
> Lock coordination for acceptors
> -------------------------------
>
> Key: ARTEMIS-5852
> URL: https://issues.apache.org/jira/browse/ARTEMIS-5852
> Project: Artemis
> Issue Type: New Feature
> Components: Broker
> Affects Versions: 2.50.0
> Reporter: Clebert Suconic
> Priority: Major
> Labels: pull-request-available
> Fix For: 2.51.0
>
> Time Spent: 5h 10m
> Remaining Estimate: 0h
>
> This opens the possibility of using Mirroring for Failover, in replacement of
> replication.
> You set a LeaderManager on the configuration, and configure Acceptors to only
> start after a distributed lock is acquired.
> this current implementation is being done on top of DistributedLockManager,
> and I'm adding etcd as an option also.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
