On Wed, Oct 22, 2014 at 10:45 AM, Gabi C <gabicr@gmail.com> wrote:Also I've gotSo Supervdsm server ocupy around 33-49% of memory alone!Hello!After upgrade from 3.4.4. to 3.5.0 I can see n all my 3 nodes
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
nod1 SPM running 0 VM
753 root 15 -5 17.208g 7.737g 10832 S 0.0 49.4 1:28.46 supervdsmServer
nod2 running 3 VM
641 root 15 -5 17.573g 7.888g 10768 S 0.0 33.5 1:17.09 supervdsmServer
nod3 running 2 VM
6391 root 15 -5 19.072g 8.646g 10844 S 9.3 44.1 38:17.05 supervdsmServer
systemctl status supervdsmd
supervdsmd.service - "Auxiliary vdsm service for running helper functions as root"
Loaded: loaded (/usr/lib/systemd/system/supervdsmd.service; static)
Active: active (running) since Tue 2014-10-21 11:32:40 EEST; 23h ago
Main PID: 753 (supervdsmServer)
CGroup: name=systemd:/system/supervdsmd.service
ââ753 /usr/bin/python /usr/share/vdsm/supervdsmServer --sockfile /var/run/vdsm/svdsm.sock
Oct 21 11:39:51 nod1 daemonAdapter[753]: Process Process-4:
Oct 21 11:39:51 nod1 daemonAdapter[753]: Traceback (most recent call last):
Oct 21 11:39:51 nod1 daemonAdapter[753]: File "/usr/lib64/python2.7/multiprocessing/process.py", line 258, in _bootstrap
Oct 21 11:39:51 nod1 daemonAdapter[753]: self.run()
Oct 21 11:39:51 nod1 daemonAdapter[753]: File "/usr/lib64/python2.7/multiprocessing/process.py", line 114, in run
Oct 21 11:39:51 nod1 daemonAdapter[753]: self._target(*self._args, **self._kwargs)
Oct 21 11:39:51 nod1 daemonAdapter[753]: File "/usr/share/vdsm/supervdsmServer", line 242, in child
Oct 21 11:39:51 nod1 daemonAdapter[753]: pipe.recv()
Oct 21 11:39:51 nod1 daemonAdapter[753]: IOError: [Errno 4] Interrupted system callAny ideeas, hints?