Francesco Saverio Castellano

thanks for the reply. There is only one problem: because right now masterB is not synced, then we only have all data in masterA and that's the master we are...

??? What kind of reply is that??? My server is used 24 hours a day, it’s a service.. so it is always busy.

hello, I'm having the same problems... i cannot get two masters with sync=mirror to fully sync. Every time the sync up to 70%-80% and then they go OUT_OF_SYNC. And this...

ok, I'm pretty sure it is not because of lack of bandwidth. Do you think I can try raising the binlog capacity from 100000000 to 200000000? How does that effect...

By the way in my case doubling the binlog capacity solved the issue and now the two ssdb instances manage to sync.

I'm adding this method in "SSDBServer". I have been looking at the code and it seems to be the correct thing to do: ``` void SSDBServer::resetSync() { log_info("resetting sync state...");...

alright, so as you said in your previous post this is just a matter of adding a "del_slave" command, for "add_slave" there is no need to add a new command...

but then I don't understand why you say: "Execute del_slave and then add_slave operation on both A and B" If I'm going to shutdown B and delete its "meta" and...

thanks! That's what I thought. I have implemented the command and tested it. So far it seems to work well. Here is my code, please tell me what you think....

The above code seems to work, however in the logs of MasterA (the master on which I have executed the new "resetslave" command) I get this: 2020-02-19 14:37:06.323 [ERROR] slave.cpp(261):...