Bug 1732717

Summary: fuse: Limit the number of inode invalidation requests in the queue
Product: [Community] GlusterFS Reporter: Nithya Balachandran <nbalacha>
Component: fuseAssignee: Nithya Balachandran <nbalacha>
Status: CLOSED NEXTRELEASE QA Contact:
Severity: medium Docs Contact:
Priority: unspecified    
Version: mainlineCC: bugs
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-08-14 03:21:50 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Nithya Balachandran 2019-07-24 08:04:16 UTC
Description of problem:

If the gluster fuse mount process is unable to process the inode invalidation requests quickly enough, the number of such invalidate_node objects rises to the point where they take a lot of memory. This defeats the purpose of invalidating inodes to control the memory used by the process.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Worker Ant 2019-07-24 09:02:18 UTC
REVIEW: https://review.gluster.org/23086 (fuse: Set limit on invalidate queue size) posted (#4) for review on master by N Balachandran

Comment 2 Worker Ant 2019-08-09 09:07:45 UTC
REVIEW: https://review.gluster.org/23187 (fuse: Set limit on invalidate queue size) posted (#1) for review on master by N Balachandran

Comment 3 Worker Ant 2019-08-14 03:21:50 UTC
REVIEW: https://review.gluster.org/23187 (fuse: Set limit on invalidate queue size) merged (#3) on master by Amar Tumballi