Bug 807271
Summary: | Client log reports every update on the "lk-version" when client grace time is expired | ||||||
---|---|---|---|---|---|---|---|
Product: | [Community] GlusterFS | Reporter: | Shwetha Panduranga <shwetha.h.panduranga> | ||||
Component: | protocol | Assignee: | Junaid <junaid> | ||||
Status: | CLOSED CURRENTRELEASE | QA Contact: | |||||
Severity: | medium | Docs Contact: | |||||
Priority: | unspecified | ||||||
Version: | mainline | CC: | gluster-bugs, vagarwal | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Whiteboard: | |||||||
Fixed In Version: | glusterfs-3.4.0 | Doc Type: | Bug Fix | ||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2013-07-24 17:33:28 UTC | Type: | --- | ||||
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: | 817967 | ||||||
Attachments: |
|
CHANGE: http://review.gluster.com/3020 (protocol/client: Set grace_timer_needed flag to false on a disconnect.) merged in master by Vijay Bellur (vijay) Bug is fixed . verified on 3.3.0qa39 |
Created attachment 573035 [details] Attaching fuse mount log file Description of problem: when server disconnects,client keeps trying to check if the server has come online to reconnect to the server for every certain period of time. when the timer is expired the client increments the lk-version. This operation need not be performed. Version-Release number of selected component (if applicable): mainline How reproducible: often Steps to Reproduce: 1.Create a replicate volume. Start the volume 2.Create fuse, nfs mounts. Start write operations on the mount point 3. Bring down one of the brick 4. Client log keeps reporting the update of lk-version as shown below. Actual results: [2012-03-27 18:36:13.614569] W [socket.c:1521:__socket_proto_state_machine] 0-dstore-client-0: reading from socket failed. Error (Transport endpoint is not connected), peer (192.168.2.35:24009) [2012-03-27 18:36:13.641103] I [client.c:136:client_register_grace_timer] 0-dstore-client-0: Registering a grace timer [2012-03-27 18:36:13.641158] I [client.c:2096:client_rpc_notify] 0-dstore-client-0: disconnected [2012-03-27 18:36:22.601509] W [socket.c:204:__socket_rwv] 0-dstore-client-3: readv failed (Connection reset by peer) [2012-03-27 18:36:22.619491] W [socket.c:1521:__socket_proto_state_machine] 0-dstore-client-3: reading from socket failed. Error (Connection reset by peer), peer (192.168.2.36:24010) [2012-03-27 18:36:24.213168] W [client.c:112:client_grace_timeout] 0-dstore-client-0: client grace timer expired, updating the lk-version to 2 [2012-03-27 18:36:24.214451] E [socket.c:1724:socket_connect_finish] 0-dstore-client-0: connection to 192.168.2.35:24009 failed (Connection refused) [2012-03-27 18:36:24.214579] I [client.c:136:client_register_grace_timer] 0-dstore-client-0: Registering a grace timer [2012-03-27 18:36:33.800410] W [client.c:112:client_grace_timeout] 0-dstore-client-3: client grace timer expired, updating the lk-version to 2 [2012-03-27 18:36:33.800806] I [client.c:136:client_register_grace_timer] 0-dstore-client-3: Registering a grace timer