Stephane VAROQUI

HI HobRKM , Yes this is intended so far replication-manager will not allow writes to happen on all master in regards to the proxies so it elect one of the...

Thanks , this bug is very hard to track, i made a new tentative to fix in my last commits can one try to reproduce with binaries in CI http://ci.signal18.io/mrm/builds/2.1/.

Work around is move to next 2.2.26 release or to disable monitoring-schema-change=false if and only if not using spider aka shard proxy or to produce analyze all database tables to...

So you been already testing last commit :) Yes that's because the slave is in io thread error , i can fix this !

Humm at the same if you have many slaves but one is having network connection issues , do you relly wan't to send traffic to it ?

I can do a test that the master is dead

Do you test commit bbf03e1 ? And still get issues ?

Oh that is after master failover i'll test this thanks

Ok i have push some changes , Consul is special case vs other proxies refresh state at every monitoring loop while with DNS only when something happen on the cluster...

If that is an old master that rejoined why would it get a replication at all? Le 16 mars 2018 13:55, "Jan" a écrit : > Following up on #216...