Hi, Pranith
> There was a time when all this clean up was not necessary because
>the mount process would die anyway. Then when gfapi came in, the process
>wouldn't die anymore :-), so we have to fix all the shortcuts we took over
>the years to properly fix it. So lot of work :-/. It is something that
>needs to be done properly (multi threaded nature of the workloads make it a
>bit difficult), because the previous attempts at fixing it caused the
>the mount process would die anyway. Then when gfapi came in, the process
>wouldn't die anymore :-), so we have to fix all the shortcuts we took over
>the years to properly fix it. So lot of work :-/. It is something that
>needs to be done properly (multi threaded nature of the workloads make it a
>bit difficult), because the previous attempts at fixing it caused the
>process to die because of double free etc.
When libgfapi used by libvirtd, the glfs_init and glfs_fini will call two times with start or stop virtual machine, and with other libvirt command like virsh domblkinfo which will visit glusterfs api, SO, as long as libvirtd start and stop vm, the libvirtd process will leak large memory, about 1.5G memory consume by 100 times call glfs_init and glfs_fini
When libgfapi used by libvirtd, the glfs_init and glfs_fini will call two times with start or stop virtual machine, and with other libvirt command like virsh domblkinfo which will visit glusterfs api, SO, as long as libvirtd start and stop vm, the libvirtd process will leak large memory, about 1.5G memory consume by 100 times call glfs_init and glfs_fini
_______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-users
