Resolving a split brain on replication

[Gr-R]

Thanks for looking it over.
We started with the defaults and modified it as a last resort to see if it would fix it.
In short, we've already tried reestablishing it using the default settings..

OK, I will dig deeper

[Gr-R]

Check the MTU on the NICs on both nodes:
eth0 at 1500 is OK, but the others need to be consistant. [9000]

san01
eth0 UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1
eth1 UP BROADCAST RUNNING SLAVE MULTICAST MTU:9216 Metric:1
eth2 UP BROADCAST RUNNING SLAVE MULTICAST MTU:9216 Metric:1
eth3 UP BROADCAST RUNNING SLAVE MULTICAST MTU:9216 Metric:1
eth4 UP BROADCAST RUNNING SLAVE MULTICAST MTU:9216 Metric:1
eth5 UP BROADCAST RUNNING SLAVE MULTICAST MTU:9000 Metric:1

san02
eth0 UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1
eth1 UP BROADCAST RUNNING SLAVE MULTICAST MTU:9216 Metric:1
eth2 UP BROADCAST RUNNING SLAVE MULTICAST MTU:9216 Metric:1
eth3 UP BROADCAST RUNNING SLAVE MULTICAST MTU:9216 Metric:1
eth4 UP BROADCAST RUNNING SLAVE MULTICAST MTU:9216 Metric:1
eth5 UP BROADCAST RUNNING SLAVE MULTICAST MTU:9216 Metric:1

[enealDC]

great find and good attention to detail! it even makes more sense because both bond0 and bond1 are in the same subnet so a [jumbo] frame could be sent from bond1 on san01 and be received by bond0 on san02. And because the default frame size for ping is 1500 mtu, that makes it seem like connectivity is good!
i'm going to make those changes and see if they fix it. i'm pretty confident at this point!

[Gr-R]

great find and good attention to detail! it even makes more sense because both bond0 and bond1 are in the same subnet so a [jumbo] frame could be sent from bond1 on san01 and be received by bond0 on san02. And because the default frame size for ping is 1500 mtu, that makes it seem like connectivity is good!
i'm going to make those changes and see if they fix it. i'm pretty confident at this point!

Let us know.
Hope it works, I confident it will

[enealDC]

Thanks! That was it.