[Bugs] [Bug 1718338] New: Upcall: Avoid sending upcalls for invalid Inode

bugzilla at redhat.com bugzilla at redhat.com
Fri Jun 7 13:59:52 UTC 2019


            Bug ID: 1718338
           Summary: Upcall: Avoid sending upcalls for invalid Inode
           Product: GlusterFS
           Version: mainline
          Hardware: All
                OS: All
            Status: NEW
         Component: upcall
          Severity: high
          Assignee: bugs at gluster.org
          Reporter: skoduri at redhat.com
                CC: bugs at gluster.org
  Target Milestone: ---
    Classification: Community

Description of problem:

For nameless LOOKUPs, server creates a new inode which shall remain invalid
until the fop is successfully processed post which it is linked to the inode

But incase if there is an already linked inode for that entry, it discards that
newly created inode which results in upcall notification. This may result in
client being bombarded with unnecessary upcalls affecting performance if the
data set is huge.

This issue can be avoided by looking up and storing the upcall context in the
original linked inode (if exists), thus saving up on those extra callbacks.

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

How reproducible:

Steps to Reproduce:

Actual results:

Expected results:

Additional info:

You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.

More information about the Bugs mailing list