[ 
https://issues.apache.org/jira/browse/ARTEMIS-3713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17504235#comment-17504235
 ] 

gayatri beela commented on ARTEMIS-3713:
----------------------------------------

with the above master - slave configuration in shared mode  we are getting  
below log (instead of Backup announced  we are getting Backup Server is live 
now)

 

AMQ221010: Backup Server is now live
2022-03-10 17:58:24,499 WARN  [org.apache.activemq.artemis.core.client] 
AMQ212034: There are more than one servers on the network broadcasting the same 
node id. You will see this message exactly once (per node) if a node is 
restarted, in which case it can be safely ignored. But if it is logged 
continuously it means you really do have more than one node on the same network 
active concurrently with the same node id. This could occur if you have a 
backup node active at the same time as its live node. 
nodeID=b7d0ba79-a06a-11ec-b9e6-005056b460eb

 

> HA with shared store not working when configured master slave in  two 
> different servers with data folder which is accessible by both servers 
> ---------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: ARTEMIS-3713
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-3713
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>    Affects Versions: 2.13.0, 2.20.0
>            Reporter: gayatri beela
>            Priority: Major
>         Attachments: broker_master.xml, broker_slave.xml
>
>
> HA with shared store not working when configured master slave in  two 
> different servers with data folder which is accessible by both servers . when 
> master is down slave is working, after that if master is again live records 
> in the queue are not processing even though we have put allow-failback true 
> in slave
> broker.xml for master and slave are attached.
>  



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

Reply via email to