[
https://issues.apache.org/jira/browse/ARTEMIS-4545?focusedWorklogId=922641&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-922641
]
ASF GitHub Bot logged work on ARTEMIS-4545:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 07/Jun/24 19:35
Start Date: 07/Jun/24 19:35
Worklog Time Spent: 10m
Work Description: AntonRoskvist commented on PR #4951:
URL:
https://github.com/apache/activemq-artemis/pull/4951#issuecomment-2155417744
Thanks for your feedback @gtully
If I am not mistaken the first case should be addressed already, where the
coordination-id takes precedence over the configured nodeID. It should be
verified by:
`org.apache.activemq.artemis.tests.integration.replication.LockManagerReplicationTest#testPrimaryPeers()`
let me know if I misunderstood though.
I will take a look at the JDBC case, thanks!
Issue Time Tracking
-------------------
Worklog Id: (was: 922641)
Time Spent: 40m (was: 0.5h)
> 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: 40m
> 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: issues-unsubscr...@activemq.apache.org
For additional commands, e-mail: issues-h...@activemq.apache.org
For further information, visit: https://activemq.apache.org/contact
