Description of problem: Currently fuse-bridge has an lru limit of the inode table as infinite. This means we are dependent on kernel to send forgets even though the inode is not active. However, we can implement garbage collection of inodes in lru list of itable. We can ask kernel to send a forget by calling inode/entry_invalidate on the inode.
REVIEW: https://review.gluster.org/19778 (fuse: add --lru-limit option) posted (#2) for review on master by Amar Tumballi
REVIEW: https://review.gluster.org/19778 (fuse: add --lru-limit option) posted (#36) for review on master by Amar Tumballi
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-6.0, please open a new bug report. glusterfs-6.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] https://lists.gluster.org/pipermail/announce/2019-March/000120.html [2] https://www.gluster.org/pipermail/gluster-users/