<div>Hi list,</div>
<div>I have a cluster with two nodes based on DRBD 0.7.24. </div>
<div> </div>
<div>Node1 <---------------------------------------> Node2</div>
<div>(Active) (Protocol C) (inActive)</div>
<div> </div>
<div>The scenario of my test case is:<br>Step 1. When a write request to the Node1 arrives, Node1 transfers the request to the local disk driver and the peer.</div>
<div>Step 2. Suppose the Node2 receives the data packets and writes to its local disk completely, but the corresponding action is delayed in Node1( maybe for some random reasons).</div>
<div>Step 3. At that very moment, Node1 is powered -off unexceptedly; the data waiting in the buffer is lost.</div>
<div>Step 4. The cluster manager promotes Node 2 from secondary to primary.</div>
<div>Step 5. Node 1 is powered-on again.</div>
<div> </div>
<div>So, the Node 2 has more on-disk data than Node 1. </div>
<div>My question is:</div>
<div>1) Will Node 2 just make a backgroud resync to Node 1 for that unfinished write request? or</div>
<div>2) Node 1 makes Node 2 to drop the result of that unfinished write request (Node 1 resync Node 2)?</div>
<div> </div>
<div>Thanks a lot.</div>
<div> </div>
<div> </div>