Daugherity, Andrew W wrote:
Message: 7
Date: Thu, 11 Aug 2011 21:07:00 +0000
From: "Daugherity, Andrew W" <adaugher...@tamu.edu>
To: "pacemaker@oss.clusterlabs.org" <pacemaker@oss.clusterlabs.org>
Subject: [Pacemaker] migration fix for ocf:heartbeat:Xen
Message-ID: <93b5e618-ad19-4993-8066-cb4f8e4ef...@tamu.edu>
Content-Type: text/plain; charset="us-ascii"

I have discovered that sometimes when migrating a VM, the migration itself will 
succeed, but the migrate_from call on the target node will fail, as apparently 
the status hasn't settled down yet.  This is more likely to happen when 
stopping pacemaker on a node, causing all its VMs to migrate away.  Migration 
succeeds, but then (sometimes) the status call in migrate_from fails, and the 
VM is unnecessarily stopped and started.  Note that it is NOT a timeout 
problem, as the migrate_from operation (which only checks status) takes less 
than a second.

I noticed the VirtualDomain RA does a loop rather than just checking the status 
once as the Xen RA does, so I patched a similar thing into the Xen RA, and that 
solved my problem.
(patch/logs snipped)


No comments?  What does it take to get this patch accepted?  I'd much rather 
use the mainline version than have to reapply my patch after every HAE update.  
I guess I could open an SR with Novell but this is ultimately an upstream issue.
I don't know about getting the patch accepted but since I've seen issues like the one you describe on my systems, I have applied your patch (Thanks!) and will see how it behaves.

--
Voiceflex
Tel 0203 301 6000 | Fax 0203 310 6700
http://getsatisfaction.com/voiceflex
www.voiceflex.com

Information contained in this e-mail is intended for the use of the 
addressee(s) only and is confidential. If you are not an addressee, note that 
any disclosure, copying, distribution, or use of the contents of this message 
is strictly prohibited. If you have received this e-mail in error, please 
contact the firm at +44 (0) 20 3301 6000 or supp...@voiceflex.com.  Any views 
or opinions expressed in this message are those of the individual sender, 
except where the sender specifically states them to be the views of Frontier 
Systems Ltd. Frontier Systems Ltd does not accept legal responsibility for this 
e-mail message due to the insecure nature of internet communications. Frontier 
Systems, 9 Warwick Street, London W1B 5LY Registered in England and Wales, No. 
03544845




_______________________________________________
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker

Reply via email to