Hi, Adrija I too have been working with trying to setup high availability and failover of active mq artemis on kubernetes cluster. The Live – Backup Groups section of this doc https://activemq.apache.org/components/artemis/documentation/latest/ha.html#high-availability-and-failover describes that only one backup server will announce as the backup. The rest will be awaiting to become a backup server. If active server goes away then the backup server will go live and a server from the backup group will be selected to be the new backup server.
Paul From: Adrija Basu <adrija.tin...@gmail.com> Date: Wednesday, December 6, 2023 at 1:25 AM To: users@activemq.apache.org <users@activemq.apache.org> Subject: Active Mq artemis hig availability and failover Hello Team I am trying to setup high availability and failover of active mq artemis on kubernetes cluster (minikube) I am using the Replication policy HA Policy: Replicated and in my kubernetes yaml file I have mentioned replica count as 3 so 3 pods are getting created 1 as master and 2 as slaves however I am noticing only for 1 slave the logs is coming as "backup announced" but for the second slave it is not coming like this as I am very new to Artemis so I want to understand is it a 1:1 mapping I mean for one liver server 1 backup server will be created? if it is so how to configure to create 1 master and multiple slaves? --Thanks And Regards *Adrija Basu*
