[
https://issues.apache.org/jira/browse/ARTEMIS-5852?focusedWorklogId=1001620&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-1001620
]
ASF GitHub Bot logged work on ARTEMIS-5852:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 23/Jan/26 22:31
Start Date: 23/Jan/26 22:31
Worklog Time Spent: 10m
Work Description: clebertsuconic opened a new pull request, #6191:
URL: https://github.com/apache/artemis/pull/6191
I'm adding a LeaderManager to the broker, that will use DistributedLock to
determine the node that will be the lead.
You can associate the leaderManager with acceptors and an acceptor serving
only clients would then be activated in only one of the brokers.
Issue Time Tracking
-------------------
Worklog Id: (was: 1001620)
Remaining Estimate: 0h
Time Spent: 10m
> 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: 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]
