[
https://issues.apache.org/jira/browse/ARTEMIS-5852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18056951#comment-18056951
]
ASF subversion and git services commented on ARTEMIS-5852:
----------------------------------------------------------
Commit 5b8b7498d9e45b5a6d29c1a5dee7099a419e8ed0 in artemis's branch
refs/heads/main from Clebert Suconic
[ https://gitbox.apache.org/repos/asf?p=artemis.git;h=5b8b7498d9 ]
ARTEMIS-5852 setLockCoordinator() should consider it null
The server is getting the configuration "" and trying to lookup for
the lockCoordinator "" that won't exist
> 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: 5.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]
