Bug 801721 - Incorrect last_sent and last_received time in statedump
Summary: Incorrect last_sent and last_received time in statedump
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: rpc
Version: mainline
Hardware: Unspecified
OS: Unspecified
medium
unspecified
Target Milestone: ---
Assignee: Amar Tumballi
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 817967
TreeView+ depends on / blocked
 
Reported: 2012-03-09 09:25 UTC by Anush Shetty
Modified: 2013-12-19 00:07 UTC (History)
2 users (show)

Fixed In Version: glusterfs-3.4.0
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-07-24 17:27:11 UTC
Regression: ---
Mount Type: fuse
Documentation: ---
CRM:
Verified Versions:
Embargoed:

Attachments (Terms of Use)

Description Anush Shetty 2012-03-09 09:25:01 UTC 
Description of problem: The  last_sent and last_received time displayed in the statedump is incorrect. 


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


How reproducible: Consistently


Steps to Reproduce:
1. kill -USR1 <pid of glusterfs>

  
Actual results:

[xlator.protocol.client.test2-client-1.priv]
connecting=0
last_sent=Thu Jan  1 05:30:00 1970

last_received=Thu Jan  1 05:30:00 1970

total_bytes_read=2092
total_bytes_written=2828

[xlator.protocol.client.test2-client-0.priv]
connecting=0
last_sent=Thu Jan  1 05:30:00 1970

last_received=Thu Jan  1 05:30:00 1970

total_bytes_read=2412
total_bytes_written=3244



Expected results: Should display the proper time


Additional info:
Comment 1 Anand Avati 2012-03-12 12:27:39 UTC 
CHANGE: http://review.gluster.com/2916 (protocol/client: remove unused variables from 'priv/conf') merged in master by Vijay Bellur (vijay)
Comment 2 Anush Shetty 2012-05-18 13:51:11 UTC 
Verified with 3.3.0qa41
Note You need to log in before you can comment on or make changes to this bug.