Bug 761933 (GLUSTER-201)

Summary: server should get notified about client 'umount'
Product: [Community] GlusterFS Reporter: Amar Tumballi <amarts>
Component: coreAssignee: Pavan Vilas Sondur <pavan>
Status: CLOSED NOTABUG QA Contact:
Severity: medium Docs Contact:
Priority: low    
Version: mainlineCC: gluster-bugs, pavan, vraman
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Amar Tumballi 2009-08-11 01:45:20 UTC 
There are many reasons why a connection between server and client may get disconnected.

Green:
1.  admin does 'umount'

Red:
2. n/w problem
3. client segfault

We should have a clear way to differentiate 'Green' and 'Red' reasons for client disconnect.

Best way to implement it is through 'notify()' framework, as notify() is cluster aware, and a given notify event gets passed on to all the translators in the graph by default.

Implement a new mop, which can pass on just these notify 'events' to server protocol from client protocol.

This is considered critical as its needed to understand the health of a client machine (which may be outside glusterfs management nodes) from server nodes.
Comment 1 Anand Avati 2009-12-02 00:48:40 UTC 
PATCH: http://patches.gluster.com/patch/2405 in master (bring new MOP called NOTIFY.)
Comment 2 Pavan Vilas Sondur 2010-08-10 06:25:24 UTC 
Marking as invalid, since it won't be implemented.