> So does that mean that -- after shutting down master and then slave --
it's not enough to start the slave again and that the master server must be
then started as well?
That's not what I'm saying.
I'm saying that if the master and slave both go down then *administrative
intervention* is require
So does that mean that -- after shutting down master and then slave -- it's
not enough to start the slave again and that the master server must be then
started as well? Because, obviously, starting the master first isn't an
option as it might have older data than its slave, right?
--
Sent from:
>From what I can tell everything is working as designed. As the
documentation [1] states:
In the replication case, the backup just keeps waiting for a live
server to pair with. Note that in replication the backup server does not
know whether any data it might have is up to date, so it really c
Hi, below my test:
1) start master and slave;
2) send two messages, stored on master;
3) stop master;
4) slave is live and it has 2 messages;
5) stop slave;
6) restart slave but i haven't previous messages;
Thanks in advance for the help!
Kind regards,
Gianfranco Aloi
--
Sent from: http://act
I don't really understand what you mean by, "If the only node to start is
the slave, i lose all information in the queue." Can you elaborate on this?
How are you losing information?
Justin
On Mon, Jun 24, 2019 at 8:37 AM galoi wrote:
> I'm using artemis ActiveMQ Artemis 2.9.0, and i configured
