Thanks all. I restarted it and that fixed the issue temporarily freeing up memory but it continued the leak process. I updated the vdsm package and that fixed it overall.
On Tue, Sep 15, 2015 at 12:57 AM Michal Skrivanek < michal.skriva...@redhat.com> wrote: > > On Sep 10, 2015, at 20:35 , Michael Kleinpaste < > michael.kleinpa...@sharperlending.com> wrote: > > > Hi everybody. > > > > So I ran into that high mem usage thing. The problem I have with > patching is that this is a live system so I can't do it mid day. Can > anybody tell me if it is possible to just restart the vdsm service or does > the host have to be in "maintenance mode" before restarting it? It is > using gluster storage, if that makes a difference as well. > > Hi, > you can restart vdsm without any effect on running VMs. Other than short > interruption of communication between engine and host. It can cause a short > CPU spike on startup, so do that with caution when you run tend or hundreds > of VMs on a same overloaded host. > Obviously, while vdsm is not running, the system is a bit more vulnerable > to failures, but as long as you don't do that in the middle of a migration > or a power failure you're good:) > > Thanks, > michal > > > > Thanks, > > -- > > Michael Kleinpaste > > Senior Systems Administrator > > SharperLending, LLC. > > www.SharperLending.com > > michael.kleinpa...@sharperlending.com > > (509) 324-1230 Fax: (509) 324-1234 > > _______________________________________________ > > Users mailing list > > Users@ovirt.org > > http://lists.ovirt.org/mailman/listinfo/users > > -- *Michael Kleinpaste* Senior Systems Administrator SharperLending, LLC. www.SharperLending.com michael.kleinpa...@sharperlending.com (509) 324-1230 Fax: (509) 324-1234
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users