just discovered another issue with "pure Master-Slave"
in 4 out of 5 test it all worked "by the book" - i.e.
when I kill MASTER, SLAVE accepgts connections and becomes a master...
but tried it out one more tiem and got this
[r...@ip-10-195-225-236 bin]# ERROR MasterConnector-
Thanks Garry
RE:
>should just ignore the slave if any replication attempt fails.
exactly!
the current way it works is that it provides "continuity" only when MASTER
fails in the pair, but not when
SLAVE fails (from what you describe it is the case when SYNC(ACKed) send is
used, but this is mo
This is true, pure master slave is asymmetrical and it requires manual
intervention to restore the paring once the master fails. There is an option
on the broker to have the master shutdown if the slave fails, but this is
off by default. The problem is that there is currently no way to have a
slave
One of the benefits of Pure Master Slave are that supposedly it provides
some "HA" -
namely books, tutorials, wiki site describe that "when MASTER fails SLAVE"
becomes a MASTER
and clients are smoothly reconnected to it via the virtue of "failover
transport"...
That is all nice and good, and TR
