y 10, 2017 4:18:35 PM
Subject: Re: problems with master slave set up artemis 2.0
Thank you Justin for the reply.
For the third case, i did both kill -9 and normal stop, and the symptom is
the same, basically the "idle" backup was not able to become an "active"
backup.
For the
Thank you Justin for the reply.
For the third case, i did both kill -9 and normal stop, and the symptom is
the same, basically the "idle" backup was not able to become an "active"
backup.
For the first two cases, if it is expected behavior, how would we expect the
replication delay or even data l
first, the secondary/"passive" slave is not
> able to take over as the "active" slave
Can you elaborate on this use-case a bit more? How are you stopping the backup?
Justin
- Original Message -----
From: "Lei"
To: users@activemq.apache.org
Sent: Tuesday, May 9,
I have a master slave non-colocation set up of one master and two slaves.
1. after all three start, only journal replication is only seen on one of
the slaves, i.e., the "active" slave.
2. try to simulate the failover scenarios.
scenario A:
- when the master is killed, the "active" slave comes up
