jbertram wrote
> The master/slave/slave triplet architecture complicates fail-back quite a
> bit and it's not something the broker handles gracefully at this point.
> I'd recommend against using it for that reason.
Would it be desirable for Artemis to support this functionality in the
future thoug
The master/slave/slave triplet architecture complicates fail-back quite a
bit and it's not something the broker handles gracefully at this point.
I'd recommend against using it for that reason.
To Clebert's point...I also don't understand why you wouldn't let the cloud
infrastructure deal with spi
I'm not sure I understand your question(s) @clebertsuconic?
We are building highly scalable systems and highly distributed systems, so
the need for the multiple backups is there to ensure that in the unlikely
event of a server or AZ failure, our systems still run at the maximum
available performan
Since you are on EC2? Why do you need a backup? Wouldn't a Storage
give you what you need in terms of Cloud? if the server is gone. .you
just start it again with the same cloud storage?
On Tue, Oct 2, 2018 at 3:22 AM schalmers
wrote:
>
> I am using AWS and paying for three EC2 instances (the 'serv
I am using AWS and paying for three EC2 instances (the 'servers'). I am
deploying a server in each AWS Availability Zone (AZ) and in the region I am
using there are 3 AZ. I am running three servers with a master (as part of a
cluster) on each, to maximum performance of the applications connecting t
