hi:<br><br><div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">> can anybody tell me if there is a way , after a split brain (caused by a
<br>> network disconnection), to tell the new node that it should sync his data<br>> with the actual primary node without having to re-syncronize all the device<br>> ? (it is too slow! aprox 1 K by sec)<br>><br>
> what im doing now is a "drbdadm invalidate all" but it tooks about 8 hours<br>> re-syncronize a 30GB partition...<br>Is this test machine or production machine? If its under test.. you can do<br>this by drbdadm command.
<br></blockquote></div><br>
in the future, both will be "production machines", one as primary and the other as a failover server. the problem is that when i disconnect the network cable from the primary server, then the drbd timeouts and (aprox 30 seconds later) the heartbeat switch the drbd to the secondary server (which gets the state Primary/Unknown). Then, when i reconnect the network cable, both nodes go in standalone mode. i would like that the "old primary" sets its state to Secondary and the replication could still be working. i think that one of the possible solutions for this is to set the drbd timeout greater than the heartbeat timeout (i will test this).
<br><br>but anyway... how can i get the old primary to forgot all his changes since the last time he was connected with the slave?<br><br>thanks in advence<br><br>--<br>Roberto Scattini<br>