[
https://issues.apache.org/jira/browse/ARTEMIS-5852?focusedWorklogId=1002344&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-1002344
]
ASF GitHub Bot logged work on ARTEMIS-5852:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 28/Jan/26 21:10
Start Date: 28/Jan/26 21:10
Worklog Time Spent: 10m
Work Description: jbertram commented on code in PR #6191:
URL: https://github.com/apache/artemis/pull/6191#discussion_r2738621494
##########
docs/user-manual/_book.adoc:
##########
@@ -65,6 +65,7 @@ include::network-isolation.adoc[leveloffset=1]
include::restart-sequence.adoc[leveloffset=1]
include::activation-tools.adoc[leveloffset=1]
include::amqp-broker-connections.adoc[leveloffset=1]
+include::lock-cordination.adoc[leveloffset=1]
Review Comment:
Typo in the name of the file. Should be `lock-coordination.adoc`.
Issue Time Tracking
-------------------
Worklog Id: (was: 1002344)
Time Spent: 3h (was: 2h 50m)
> 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: 3h
> 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]
