[
https://issues.apache.org/jira/browse/ARTEMIS-4545?focusedWorklogId=922811&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-922811
]
ASF GitHub Bot logged work on ARTEMIS-4545:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 10/Jun/24 12:50
Start Date: 10/Jun/24 12:50
Worklog Time Spent: 10m
Work Description: gtully commented on PR #4951:
URL:
https://github.com/apache/activemq-artemis/pull/4951#issuecomment-2158260584
> @gtully Do you know of any current test that demonstrates (or at least
includes) having to wait for a lease expiry for the JDBC case?
https://github.com/apache/activemq-artemis/blob/362dbd11ac132e66f7bce99eb0fb4aa020346210/artemis-server/src/test/java/org/apache/activemq/artemis/core/server/impl/jdbc/JdbcLeaseLockTest.java#L218
that looks like it should have to wait.
Issue Time Tracking
-------------------
Worklog Id: (was: 922811)
Time Spent: 1h (was: 50m)
> 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: 1h
> 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
