[
https://issues.apache.org/jira/browse/ARTEMIS-5852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18055242#comment-18055242
]
ASF subversion and git services commented on ARTEMIS-5852:
----------------------------------------------------------
Commit 09aa18e9302f437a5f1e401aaf7c8c6e4258dac1 in artemis's branch
refs/heads/main from Clebert Suconic
[ https://gitbox.apache.org/repos/asf?p=artemis.git;h=09aa18e930 ]
Revert "ARTEMIS-5852 Lock coordination for acceptors"
This reverts commit 98dd1bafd9100deeb5fd272a7c44ae5a88bfce4d.
I'm reverting to reapply without the type and keep the previous
reflection code
> 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: 4h 40m
> 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]
