WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-api

[Xen-API] Re: ovs-vswitchd high cpu and memory use eventually crashes

To: "Andres E. Moya" <amoya@xxxxxxxxxxxxxxxxx>
Subject: [Xen-API] Re: ovs-vswitchd high cpu and memory use eventually crashes
From: Ben Pfaff <blp@xxxxxxxxxx>
Date: Thu, 8 Sep 2011 09:30:14 -0700
Cc: "Andres E. Moya" <public-amoya-6IoTNRIFf+UAspv4Qr0y0gC/G2K4zDHf@xxxxxxxxxxxxxxx>, public-xen-api-GuqFBffKawuULHF6PoxzQEEOCMrvLtNR@xxxxxxxxxxxxxxx
Delivery-date: Fri, 09 Sep 2011 17:30:46 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <a9cdae68-19ff-4188-88e4-dee340076f6a@mbs01>
List-help: <mailto:xen-api-request@lists.xensource.com?subject=help>
List-id: Discussion of API issues surrounding Xen <xen-api.lists.xensource.com>
List-post: <mailto:xen-api@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-api>, <mailto:xen-api-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-api>, <mailto:xen-api-request@lists.xensource.com?subject=unsubscribe>
References: <20110908140652.GE24127@xxxxxxxxxx> <a9cdae68-19ff-4188-88e4-dee340076f6a@mbs01>
Sender: xen-api-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.21 (2010-09-15)


It doesn't make sense that the number of CPUs would make a difference
for OVS userspace (which is all that "restart" affects), because OVS
userspace is not multithreaded.

On Thu, Sep 08, 2011 at 12:12:06PM -0400, Andres E. Moya wrote:
> Ben,
> I ran /etc/init.d/openvswitch restart and it gave me a warning if i wanted to 
> restart it, I hit y and it restarted and everything went back to normal.
> 
> So it seems there is a correlation between running xen with
> echo "NR_DOMAIN0_VCPUS=1" > /etc/sysconfig/unplug-vcpus
> and openvswitch not consuming cpu and memory then crashing, it does it a 
> slower pace when run with "NR_DOMAIN0_VCPUS=1 instead of "NR_DOMAIN0_VCPUS=4
> 
> does anyone know if these issues are being addressed on the release that is 
> supposed to be due out tomorrow?
> 
> 
> ----- Original Message -----
> From: "Ben Pfaff" <blp@xxxxxxxxxx>
> To: "Andres E. Moya" <amoya@xxxxxxxxxxxxxxxxx>
> Cc: public-xen-api-GuqFBffKawuULHF6PoxzQEEOCMrvLtNR@xxxxxxxxxxxxxxx, "Andres 
> E. Moya" <public-amoya-6IoTNRIFf+UAspv4Qr0y0gC/G2K4zDHf@xxxxxxxxxxxxxxx>
> Sent: Thursday, September 8, 2011 10:06:52 AM
> Subject: Re: ovs-vswitchd high cpu and memory use eventually crashes
> 
> If OVS is running with --monitor (as it does by default on XenServer),
> then you can restart it quickly with just "kill -SEGV $(cat
> /var/run/ovs-vswitchd.conf)".  Yes, it will just pause connectivity
> briefly.
> 
> On Thu, Sep 08, 2011 at 06:14:47AM -0400, Andres E. Moya wrote:
> > is there anyway to restart the ovs-vswitchd process, will this jsut
> > kill connectivity while it is restarting?
> > 
> > ----- Original Message -----
> > From: "Ben Pfaff" <blp@xxxxxxxxxx>
> > To: "Andres E. Moya" 
> > <public-amoya-6IoTNRIFf+UAspv4Qr0y0gC/G2K4zDHf@xxxxxxxxxxxxxxx>
> > Cc: public-xen-api-GuqFBffKawuULHF6PoxzQEEOCMrvLtNR@xxxxxxxxxxxxxxx
> > Sent: Wednesday, September 7, 2011 10:11:39 PM
> > Subject: Re: ovs-vswitchd high cpu and memory use eventually crashes
> > 
> > 
> > 
> > "Andres E. Moya"
> > <amoya-6IoTNRIFf+UAspv4Qr0y0gC/G2K4zDHf@xxxxxxxxxxxxxxxx> writes:
> > 
> > > we tried the fix
> > > echo "NR_DOMAIN0_VCPUS=1" > /etc/sysconfig/unplug-vcpus
> > >
> > > 24 hours later the same thing happened
> > 
> > The symptoms sound like a small per-flow memory leak.  When I get
> > a chance, I'll test for that.  (Or you can do so yourself with
> > --leak-check and ovs-parse-leaks and send a patch.)
> > 
> > 
> > 
> 
> 



_______________________________________________
xen-api mailing list
xen-api@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/mailman/listinfo/xen-api

<Prev in Thread] Current Thread [Next in Thread>