[
https://issues.apache.org/jira/browse/ARTEMIS-4545?focusedWorklogId=922137&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-922137
]
ASF GitHub Bot logged work on ARTEMIS-4545:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 05/Jun/24 11:15
Start Date: 05/Jun/24 11:15
Worklog Time Spent: 10m
Work Description: gtully commented on PR #4951:
URL:
https://github.com/apache/activemq-artemis/pull/4951#issuecomment-2149567599
Have you seen:
https://github.com/apache/activemq-artemis/blob/576622571a839720d83d800b12a7f2b2448b30d9/artemis-server/src/main/java/org/apache/activemq/artemis/core/server/impl/ReplicationPrimaryActivation.java#L171
with the zk locker we can have peer brokers that coordinate on a shared node
id. it is called the coordinator-id in the zk activation config, but ends up as
the node-id. With the potential for unknown backups with replication, the node
id has to be reset. However this new config could make it simpler for pure
peers, where there is no replication b/c the it is non persistent or uses a
shared store.
I guess we need to allow these to coexist or document that they must be used
independently.
Issue Time Tracking
-------------------
Worklog Id: (was: 922137)
Time Spent: 20m (was: 10m)
> Allow node ID to be configured
> ------------------------------
>
> Key: ARTEMIS-4545
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4545
> Project: ActiveMQ Artemis
> Issue Type: New Feature
> Reporter: Justin Bertram
> Assignee: Justin Bertram
> Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> In certain situations it would be beneficial to configure the node ID rather
> than having it automatically generated.
> For example, when using replication + failback if the primary server fails
> the backup will take over. Then when the primary is restarted it will
> initiate failback. However, if the primary broker's journal is damaged or
> lost during the initial failure then it won't be able to initiate failback
> because it won't have the same node ID as the backup. This kind of situation
> is not uncommon in cloud environments where there is no persistent, attached
> storage.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information, visit: https://activemq.apache.org/contact
