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

bugzilla at redhat.com bugzilla at redhat.com
Fri Jun 14 12:09:10 UTC 2019


            Bug ID: 1720634
           Summary: Upcall: Avoid sending upcalls for invalid Inode
           Product: GlusterFS
           Version: 5
          Hardware: All
                OS: All
            Status: NEW
         Component: upcall
          Keywords: Triaged
          Severity: high
          Assignee: bugs at gluster.org
          Reporter: skoduri at redhat.com
                CC: bugs at gluster.org
        Depends On: 1718338
            Blocks: 1717784, 1720633
  Target Milestone: ---
    Classification: Community

+++ This bug was initially created as a clone of Bug #1718338 +++

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:

--- Additional comment from Worker Ant on 2019-06-07 14:10:52 UTC ---

REVIEW: https://review.gluster.org/22840 (upcall: Avoid sending notifications
for invalid inodes) posted (#1) for review on master by soumya k

Referenced Bugs:

[Bug 1717784] Ganesha-gfapi logs are flooded with error messages related to
"gf_uuid_is_null(gfid)) [Invalid argument]" when lookups are running from
multiple clients
[Bug 1718338] Upcall: Avoid sending upcalls for invalid Inode
[Bug 1720633] Upcall: Avoid sending upcalls for invalid Inode
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