If you have (or add, even if you don't use it) an ELB in front of the cluster's ASG, and you configure a health check on the ELB that can only be passed when the broker is alive, and you configure the ASG's HealthCheckType to be "ELB", then AWS will terminate your EC2 when the broker process stops due to the type of situation you describe.
Tim On Fri, Mar 1, 2019, 6:44 AM <jo.stenb...@offilive.com> wrote: > Thanks Justin, I will have a look at the import/export function. this > might work for us. > > AWS will not restart the EC2 instance if a process failure happens (JVM > crash). > Also the backup server is in a separate Availability Zone in case the > whole AZ with the master goes down. > > Jo > > February 27, 2019 3:04 PM, "Justin Bertram" <jbert...@apache.org> wrote: > > > Take a look at the export/import functionality available from the CLI. > > > > Out of curiosity, will AWS not restart a node if it goes down and if so > > wouldn't that mitigate the need for a backup? > > > > Justin > > > > On Wed, Feb 27, 2019 at 4:12 AM <jo.stenb...@offilive.com> wrote: > > > >> Hi, > >> > >> we are using Artemis 2.6 clusters in AWS where a cluster consists of a > >> master and one backup server. For upgrades we are using a blue/green > >> deployment scheme where we setup a new cluster on two new server > instances, > >> perform functional tests etc and once done switch the loadbalancer in > front > >> of Artemis from the old cluster to the new cluster. > >> > >> Now we are trying to find an easy way to migrate all messages from the > old > >> cluster to the new cluster. > >> > >> I looked at Core Bridges but they require manual configuration for each > >> source/target address. We however have a lot autocreated > addresses/queues. > >> > >> Any ideas? > >> > >> Thanks, > >> Jo >
