Bug 1200264

Summary: Upcall: Support to handle upcall notifications asynchronously
Product: [Community] GlusterFS Reporter: Soumya Koduri <skoduri>
Component: upcallAssignee: Soumya Koduri <skoduri>
Status: CLOSED WONTFIX QA Contact:
Severity: high Docs Contact:
Priority: unspecified    
Version: mainlineCC: bugs, pgurusid
Target Milestone: ---Keywords: Triaged
Target Release: ---   
Hardware: All   
OS: All   
Whiteboard: FutureFeature
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-04-17 15:40:00 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:
Embargoed:
Bug Depends On:    
Bug Blocks: 1200262    

Description Soumya Koduri 2015-03-10 07:25:43 UTC 
Description of problem:

This is with respect to one of the review comments received - 
http://review.gluster.org/#/c/9535/9/xlators/features/upcall/src/upcall-internal.c

Add support to send upcall notifications asynchronously.
Comment 1 Yaniv Kaul 2019-04-17 09:28:36 UTC 
Status?
Comment 2 Soumya Koduri 2019-04-17 13:22:11 UTC 
Still a todo..No one has worked on it yet.

Also since upcall notifications are now consumed by multiple cache layers (like md-cache, nl-cache etc) and not just nfs-ganesha, we need to check with those xlator maintainers if making them asynchronous doesn't pose any issue wrt cache-coherency expected.
Comment 3 Yaniv Kaul 2019-04-17 13:45:07 UTC 
(In reply to Soumya Koduri from comment #2)
> Still a todo..No one has worked on it yet.
> 
> Also since upcall notifications are now consumed by multiple cache layers
> (like md-cache, nl-cache etc) and not just nfs-ganesha, we need to check
> with those xlator maintainers if making them asynchronous doesn't pose any
> issue wrt cache-coherency expected.

Since this was filed ~4 years ago - do we expect anyone to work on this?