Hello,

We have been running artemis 2.17 with replication HA policy (1 master and
1 slave) in kubnernetes for a few months. I was advised to run artemis
without HA in kubernetes since pod will be restarted anyway but my setup
was a team decision so I did not make any change. Recently we had a few
incidents in which the master went down or both the mater and slave when
down at the same time. In all cases, the sender and the consumer throw
exception that connection to broker was interrupted. This means connection
does not seamlessly transfer to slave but requires the client to reconnect,
same as if I don't have replica configured and only rely on kubernetes pod
restart. The only disadvantage of not having replica is the longer downtime
since kubernetes may take a minute to restart the pod. So, with that, is
the recommended way to run Artemis in kubernetes to be without HA still
hold?

Regards

Thai Le

Reply via email to