I also thought that bringing slave first before master would solve the problem,
but it didn’t ...
Slave waits with a message
"AMQ221109: Apache ActiveMQ Artemis Backup Server version 2.6.2 [null] started,
waiting live to fail before it gets active"
as soon as master is started it says
You could have another passive backup that would assume when M1 is
killed and it could become the backup.
But if the node is alone and you killed it. you need to start it first.
On Wed, Jul 18, 2018 at 9:27 AM, Clebert Suconic
wrote:
> At the moment you have to start the latest server to be
At the moment you have to start the latest server to be alive first.
I know there's a task to compare age of the journals before
synchronizing it.. but it's not done yet.
On Tue, Jul 17, 2018 at 6:48 PM, Udayan Sahu wrote:
> Its simple HA subsystem, with a simple ask in replicated state system,
Its simple HA subsystem, with a simple ask in replicated state system, it
should start from last committed state…
Step1: Master (M1) & Standby (S1) Alive
Step2: Producer Send 10 Message à M1 receives it and replicates it to S1
Step3: Kill Master ( M1) à It makes S1 as New Master
Step4:
Ha is about preserving the journals between failures.
When you read and send messages you may still have an failure during the
reading. I would need to understand what you do in case of a failure with
your consumer and producer.
Retries on send and duplicate detection are key for your case.
Hi,
We are setting up a cluster of 6 brokers using Artemis 2.6.2.
The cluster has 3 groups.
- Each group has one master, and one slave broker pair.
- The HA uses replication.
- Each master broker configuration has the flag 'check-for-live-server' set to
true.
- Each slave broker
