Hello Francois<br><br>can you post your cluster configuration using pastebin?<br><br>Thanks<br><br><div class="gmail_quote">2012/5/1 Francois Gaudreault <span dir="ltr"><<a href="mailto:fgaudreault@inverse.ca" target="_blank">fgaudreault@inverse.ca</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
<br>
I am not sure if this is the right mailing list to post for our problems, let me know if this is more a Corosync issue.<br>
<br>
We are facing a weird behavior with Corosync/Pacemaker/DRBD, and I expect to have some inputs and help to troubleshoot what is going on. Let me try to explain the best I can what we do.<br>
<br>
We have a cluster with two node using DRBD running SQL stuff. We do have a location constraint that tells Pacemaker that DRBD should be primary on NODE A when able. When we migrate the services to NODE B, and we reboot NODE A, we are facing split brains every single time.<br>
<br>