Thanks for the insight Justin.
Albert
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
> Speaking of split brains, I haven't really been able to discern how to
> recover from a split brain. What are the general techniques to recovering
> from a split brain?
Recovering from a split-brain may be impossible depending on what happens
during the split and what kind of logging you have in
Thanks for the quick response Justin.
I've configured Artemis to use replication as the infrastructure for
shared-storage isn't... great.
So for my situation at work, the hypervisors tend to randomly die on us (and
thus taking the VMs with them). We have 3 zones/hypervisors.
I wanted a single ma
This is a valid setup even though failback won't work as expected. There
should be no more risk of data loss in this setup as there is in any other.
Justin
On Thu, Jun 6, 2019 at 2:49 AM Bummer wrote:
> This isn't a valid setup. Only one slave per master can work as expected.
> You're about to
At this point using multiple backups will preclude fail-back from working
as generally expected so the behavior you're seeing is expected.
Out of curiosity, are you using shared-storage or replication? If you're
using replication keep in mind that you'll want at least 3 master/slave
pairs to achie
This isn't a valid setup. Only one slave per master can work as expected.
You're about to lose data if you continue this way. I was there recently.
Look this topic up on the forums to get more information about the reasons.
This setup is surprisingly common.
--
Sent from: http://activemq.2283324
I just want to confirm that this is the expected behaviour. I have 1 master
with 3 slaves (the brokers are hosted on VMs that tend to randomly die). I'm
currently testing this on the latest source code from github.
Here's the scenario:
1) Start master
2) Start slave1
3) Start slave2
4) Kill maste
