Hi Felix, this is the expected behaviour because the other broker competing for the lock may modify the state as FAILINGBACK when it starts so ensure the state is ACTIVE before returning true, see https://github.com/apache/activemq-artemis/blob/2.39.0/artemis-server/src/main/java/org/apache/activemq/artemis/core/server/impl/FileLockNodeManager.java#L569
Regards, Domenico On Thu, 6 Mar 2025 at 08:34, Felix Buergler (Suva) <felix.buerg...@suva.ch.invalid> wrote: > Hi all, > > > > We run AMQ 2.39.0 with NFS shared-store ha-policy. > > NFS Service is based on Hitachi HNAS Cluster. When NFS Share is moved > online to the other site, our AMQ Backup takes over and Primary is > terminating. > > > > Is there a way to remain Primary “warm standby” without terminating the > process and failback to Primary? > > Or even better, not to loose the primary Role, when > /nfsfpamb/amqt01/data/journal/server.lock > get’s a new timestamp. > > > > Primary: > > <name>amq-snbx-intranet</name> > > <persistence-enabled>true</persistence-enabled> > > > > <ha-policy> > > <shared-store> > > <primary> > > <failover-on-shutdown>true</failover-on-shutdown> > > </primary> > > </shared-store> > > </ha-policy> > > > > <!-- Resource-Manager transaction-timeout 12min, wegen 10min > tx-timeout pdf-server --> > > <transaction-timeout>1800000</transaction-timeout> > > > > <!-- Connectors --> > > > > <connectors> > > <connector name="netty-connector">tcp://node1:63616</connector> > > <connector > name="netty-backup-connector">tcp://node2:63616</connector> > > </connectors> > > > > <!-- Acceptors --> > > <acceptors> > > <acceptor > name="netty-acceptor">tcp://node1:63616?amqpMinLargeMessageSize=512000</acceptor> > > </acceptors> > > > > <cluster-connections> > > <cluster-connection name="amq-snbx-intranet"> > > <connector-ref>netty-connector</connector-ref> > > <static-connectors> > > <connector-ref>netty-backup-connector</connector-ref> > > </static-connectors> > > </cluster-connection> > > </cluster-connections> > > > > > > > > > > Backup: > > <name>amq-snbx-intranet</name> > > <persistence-enabled>true</persistence-enabled> > > > > <ha-policy> > > <shared-store> > > <backup> > > <allow-failback>true</allow-failback> > > </backup> > > </shared-store> > > </ha-policy> > > > > <!-- Resource-Manager transaction-timeout 12min, wegen 10min > tx-timeout pdf-server --> > > <transaction-timeout>1800000</transaction-timeout> > > > > <!-- Connectors --> > > > > <connectors> > > <connector > name="netty-live-connector">tcp://node1:63616</connector> > > <connector name="netty-connector">tcp://node2:63616</connector> > > </connectors> > > > > <!-- Acceptors --> > > <acceptors> > > <acceptor > name="netty-acceptor">tcp://node2:63616?amqpMinLargeMessageSize=512000</acceptor> > > </acceptors> > > > > <cluster-connections> > > <cluster-connection name="amq-snbx-intranet"> > > <connector-ref>netty-connector</connector-ref> > > <static-connectors> > > <connector-ref>netty-live-connector</connector-ref> > > </static-connectors> > > </cluster-connection> > > </cluster-connections> > > > > Regards, Felix > > ------------------------------ > > Disclaimer: > > Diese Nachricht und ihr eventuell angehängte Dateien sind nur für den > Adressaten bestimmt. Sie kann vertrauliche oder gesetzlich geschützte Daten > oder Informationen beinhalten. Falls Sie diese Nachricht irrtümlich > erreicht hat, bitten wir Sie höflich, diese unter Ausschluss jeglicher > Reproduktion zu löschen und die absendende Person zu benachrichtigen. Danke > für Ihre Hilfe. > > This message and any attached files are for the sole use of the recipient > named above. It may contain confidential or legally protected data or > information. If you have received this message in error, please delete it > without making any copies whatsoever and notify the sender. Thank you for > your assistance. >
