[
https://issues.apache.org/jira/browse/ARTEMIS-5852?focusedWorklogId=1002341&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-1002341
]
ASF GitHub Bot logged work on ARTEMIS-5852:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 28/Jan/26 21:08
Start Date: 28/Jan/26 21:08
Worklog Time Spent: 10m
Work Description: jbertram commented on code in PR #6191:
URL: https://github.com/apache/artemis/pull/6191#discussion_r2738615615
##########
docs/user-manual/lock-cordination.adoc:
##########
@@ -0,0 +1,159 @@
+= Lock Coordination
+:idprefix:
+:idseparator: -
+:docinfo: shared
+
+The Lock Manager provides pluggable distributed lock mechanism monitoring.
Review Comment:
Should say, "Lock Coordinator," instead of "Lock Manager."
Issue Time Tracking
-------------------
Worklog Id: (was: 1002341)
Time Spent: 2.5h (was: 2h 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: 2.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]
