[
https://issues.apache.org/jira/browse/ARTEMIS-5852?focusedWorklogId=1002350&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-1002350
]
ASF GitHub Bot logged work on ARTEMIS-5852:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 28/Jan/26 21:22
Start Date: 28/Jan/26 21:22
Worklog Time Spent: 10m
Work Description: jbertram commented on PR #6191:
URL: https://github.com/apache/artemis/pull/6191#issuecomment-3814003443
The commit message refers to both "Leader/Follower" and "LockMonitor." I
might suggest something like this:
```
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.
```
Issue Time Tracking
-------------------
Worklog Id: (was: 1002350)
Time Spent: 3.5h (was: 3h 20m)
> Leader/Follower pattern on 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: 3.5h
> 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]
