[
https://issues.apache.org/jira/browse/ARTEMIS-4545?focusedWorklogId=921548&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-921548
]
ASF GitHub Bot logged work on ARTEMIS-4545:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 31/May/24 14:09
Start Date: 31/May/24 14:09
Worklog Time Spent: 10m
Work Description: AntonRoskvist opened a new pull request, #4951:
URL: https://github.com/apache/activemq-artemis/pull/4951
This turned out to be quite a bit more involved than what I originally
anticipated, please let me know if anything is missing or is otherwise looking
strange
Issue Time Tracking
-------------------
Worklog Id: (was: 921548)
Remaining Estimate: 0h
Time Spent: 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: 10m
> 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
