You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2025/07/09 10:24:00 UTC
[jira] [Work logged] (ARTEMIS-4545) Allow node ID to be configured
[ https://issues.apache.org/jira/browse/ARTEMIS-4545?focusedWorklogId=973957&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-973957 ]
ASF GitHub Bot logged work on ARTEMIS-4545:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 09/Jul/25 10:23
Start Date: 09/Jul/25 10:23
Worklog Time Spent: 10m
Work Description: jsmucr commented on PR #4951:
URL: https://github.com/apache/activemq-artemis/pull/4951#issuecomment-3052081604
Any potential updates on this?
Today I've come across this when replacing a master node with an entirely new one, and despite the configuration being correct, I was left with two live nodes instead of a live node and a replica.
Issue Time Tracking
-------------------
Worklog Id: (was: 973957)
Time Spent: 1h 10m (was: 1h)
> 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
> Labels: pull-request-available
> Time Spent: 1h 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: issues-unsubscribe@activemq.apache.org
For additional commands, e-mail: issues-help@activemq.apache.org
For further information, visit: https://activemq.apache.org/contact