You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@artemis.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2026/01/29 21:37:00 UTC
[jira] [Work logged] (ARTEMIS-5852) Lock coordination for acceptors
[ https://issues.apache.org/jira/browse/ARTEMIS-5852?focusedWorklogId=1002583&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-1002583 ]
ASF GitHub Bot logged work on ARTEMIS-5852:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 29/Jan/26 21:36
Start Date: 29/Jan/26 21:36
Worklog Time Spent: 10m
Work Description: clebertsuconic commented on PR #6203:
URL: https://github.com/apache/artemis/pull/6203#issuecomment-3820502284
this is re-sending https://github.com/apache/artemis/pull/6191, since I reverted it to remove the type on the configuration.
Issue Time Tracking
-------------------
Worklog Id: (was: 1002583)
Time Spent: 5h (was: 4h 50m)
> Lock coordination for 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: 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: issues-unsubscribe@artemis.apache.org
For additional commands, e-mail: issues-help@artemis.apache.org