RE: Artemis deployment in AWS

[Jan Šmucr <Ja...@aimtecglobal.com>]

Hello.

We too are trying to switch from replication to a more simple model, especially when it comes to single master-slave pair cluster model which suffers from split brain issues. AWS EFS and the shared storage model makes sense.
The idea is that before we expand our cluster, there would be only one master and one slave node, both in a different AZ with EFS based storage shared amongst these AZs.
Are there any drawbacks? Are the storage locks reliable so that no split brain situation occurs even if the two AZs stop communicating between each other?

Looking forward to hearing some input. 🙂
Jan

On 2020/11/25 13:10:36 Luis De Bello wrote:
> Hi guys,
>
> I would like to know your experience operating an Artemis cluster in AWS, is anyone doing that? how do you handle the broker state? EFS, JDBC?
>
> Currently we have 4 instances in production (EC2 instances) using disk state and we avoid destroying instances using termination policies (to avoid lossing messages), during releases we mount extra instances lets say 4 more and we wait until message distribution moves messages from old instances to new one.
>
> It is working fine, but it has the drawback of avoiding the instances going down when something fails like, OOM, topology issues leading us to execute manual restart, so we are looking to move to a differnet model, options are externalizaing state or doing the broker stateless and repopulating messages.
>
> I would like to hear about your deployment models and similar issues.
>
> Regards,
> Luis
>

Re: Artemis deployment in AWS

[Justin Bertram <jb...@apache.org>]

Typically in a cloud environment like AWS you'd let the environment itself
restart any failed broker instances so that HA isn't even necessary. Also,
if you want redundancy between disparate locations (e.g. different
availability zones) I'd recommend mirroring [1]. Normal HA solutions (e.g.
shared storage or replication) are really designed to be used on local
networks with very low latency.


Justin

[1]
https://activemq.apache.org/components/artemis/documentation/latest/amqp-broker-connections.html#mirroring

On Wed, Jul 20, 2022 at 6:12 AM Jan Šmucr <Ja...@aimtecglobal.com>
wrote:

> Hello.
>
> We too are trying to switch from replication to a more simple model,
> especially when it comes to single master-slave pair cluster model which
> suffers from split brain issues. AWS EFS and the shared storage model makes
> sense.
> The idea is that before we expand our cluster, there would be only one
> master and one slave node, both in a different AZ with EFS based storage
> shared amongst these AZs.
> Are there any drawbacks? Are the storage locks reliable so that no split
> brain situation occurs even if the two AZs stop communicating between each
> other?
>
> Looking forward to hearing some input. 🙂
> Jan
>
> On 2020/11/25 13:10:36 Luis De Bello wrote:
> > Hi guys,
> >
> > I would like to know your experience operating an Artemis cluster in
> AWS, is anyone doing that? how do you handle the broker state? EFS, JDBC?
> >
> > Currently we have 4 instances in production (EC2 instances) using disk
> state and we avoid destroying instances using termination policies (to
> avoid lossing messages), during releases we mount extra instances lets say
> 4 more and we wait until message distribution moves messages from old
> instances to new one.
> >
> > It is working fine, but it has the drawback of avoiding the instances
> going down when something fails like, OOM, topology issues leading us to
> execute manual restart, so we are looking to move to a differnet model,
> options are externalizaing state or doing the broker stateless and
> repopulating messages.
> >
> > I would like to hear about your deployment models and similar issues.
> >
> > Regards,
> > Luis
> >
>