Gluster users - Feb 2019 - Memory management, OOM kills and glusterfs

All,

Me, Csaba and Manoj are presenting our experiences with using FUSE as an
interface for Glusterfs at Vault'19 [1]. One of the areas Glusterfs has
faced difficulties is with memory management. One of the reasons for high
memory consumption has been the amount of memory consumed by glusterfs
mount process to maintain the inodes looked up by the kernel. Though we've
a solution [2] for this problem, things would've been much easier and
effective if Glusterfs was in kernel space (for the case of memory
management). In kernel space, the memory consumed by inodes would be
accounted for kernel's inode cache and hence kernel memory management would
manage the inodes more effectively and intelligently. However, being in
userspace there is no way to account the memory consumed for an inode in
user space and hence only a very small part of the memory gets accounted
(the inode maintained by fuse kernel module).

The objective of this mail is to collect more cases/user issues/bugs such
as these so that we can present them as evidence. I am currently aware of a
tracker issue [3] which covers the issue I mentioned above.

Also, if you are aware of any other memory management issues, we are
interested in them.

[1] https://www.usenix.org/conference/vault19/presentation/pillai
[2] https://review.gluster.org/#/c/glusterfs/+/19778/
[3] https://bugzilla.redhat.com/show_bug.cgi?id=1647277
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.gluster.org/pipermail/gluster-users/attachments/20190204/f1f39904/attachment.html>