[Bugs] [Bug 1261882] New: Protocol/client registers grace_timer for disconnect to glusterd

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1261882

            Bug ID: 1261882
           Summary: Protocol/client registers grace_timer for disconnect
                    to glusterd
           Product: GlusterFS
           Version: mainline
         Component: protocol
          Severity: low
          Assignee: bugs at gluster.org
          Reporter: achiraya at redhat.com
                CC: bugs at gluster.org, gluster-bugs at redhat.com



Description of problem:
When lock-heal is enabled for a volume, grace_timer is registered during
disconnect received by client translator after a portmap query. This was
discovered in client logs as follows.

. . .
[2015-09-10 10:47:41.114371] D [MSGID: 0] [client.c:2027:client_rpc_notify]
0-vol-client-0: got RPC_CLNT_DISCONNECT
[2015-09-10 10:47:41.114446] I [MSGID: 114004]
[client.c:197:client_register_grace_timer] 0-vol-client-0: Registering a grace
timer
. . .

And this grace_timer is cancelled immediately following the connect to
glusterfsd.

[2015-09-10 10:47:41.121995] D [MSGID: 0] [client.c:1987:client_rpc_notify]
0-vol-client-0: got RPC_CLNT_CONNECT
. . .
[2015-09-10 10:47:41.122688] W [MSGID: 114005]
[client.c:2014:client_rpc_notify] 0-vol-client-0: Cancelling the grace timer
. . .

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

How reproducible:
100%

Steps to Reproduce:
1. Create a 1-brick volume.
2. Set client log level to DEBUG
gluster volume set <VOLNAME> client-log-level DEBUG
3. Enable lock-healing
gluster volume set <VOLNAME> lock-heal on
4. Mount the volume.
5. Check mount log for the above mentioned entries.

Actual results:
grace_timer was registered.

Expected results:
grace_timer should not be registered.

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