Hi,
+1 from me on the recommendations regarding Artemis on Kubernetes from core
developers.
I can only share how we are currently doing our HA.
I've invested weeks of my time to investigate regarding having master/slave
Artemis shared disk cluster with the following configurations:
1) Artemis HA on VM machines (GCE or similar).
2) Artemis HA on Kubernetes (GKE or similar).
3) Artemis HA with Operator under Kubernetes.
4) Artemis without HA config and just leave HA for Kubernetes and Cloud load
balancer.
We went with option 1) because as far as I far as I could gather info:
* Option 2 requires shared storage with Kubernetes which is not available on
any cloud provider. You must hack some kind of Kubernetes system with Ceth or
glusterfs support yourself.
* Option 3 is early alpha and the stability could be questionable
* Option 4 is not really HA solution because if a nodes attached to persistent
storage fails you will have to somehow redeploy different PVC config on
different node manually, or you again must have a shared disk solution which is
not available on any cloud provider.
Our option 1 is configured on GCE with a shared NetApp NFS4.1 volume support.
So far we are happy with stability. NetApp pricing could be better though ð
It would be interesting to know what others are doing, especially when talking
about Google Cloud?
--
Vilius
-----Original Message-----
From: Jo De Troy <jo.de.t...@gmail.com>
Sent: Thursday, February 10, 2022 12:55 PM
To: users@activemq.apache.org
Subject: Re: Artemis high availability in Kubernetes
Hello,
I'm also interested in the recommended setup on Kubernetes for a HA ActiveMQ
Artemis broker.
What is possible, what is not? Active/Passive setup is that possible/supported
on Kubernetes, or does that not make sense?
What is recommended?
Best Regards,
Jo
Op wo 9 feb. 2022 om 19:00 schreef Thai Le <lnthai2...@gmail.com>:
> 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
>
