[
https://issues.apache.org/jira/browse/ARTEMIS-5852?focusedWorklogId=1002036&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-1002036
]
ASF GitHub Bot logged work on ARTEMIS-5852:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 27/Jan/26 16:26
Start Date: 27/Jan/26 16:26
Worklog Time Spent: 10m
Work Description: gtully commented on PR #6191:
URL: https://github.com/apache/artemis/pull/6191#issuecomment-3806164126
I am not sure we need an etcd impl and extra dep at this point, the existing
zk impl is sufficient and well proven.
We can add file and jdbc to allow the existing store lockers to mix and
match.
At some point we can do a kube impl and layer over the kube api server
leader election api when it comes out of a feature flag. this looks great.
Issue Time Tracking
-------------------
Worklog Id: (was: 1002036)
Time Spent: 1h 20m (was: 1h 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: 1h 20m
> 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]
