Bug 1258411

Summary:	trace xlator: Print write size also in trace_writev logs
Product:	[Community] GlusterFS	Reporter:	Krutika Dhananjay <kdhananj>
Component:	trace	Assignee:	Krutika Dhananjay <kdhananj>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	low	Docs Contact:
Priority:	medium
Version:	3.7.3	CC:	bugs, gluster-bugs
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-3.7.5	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1258311	Environment:
Last Closed:	2015-10-14 10:30:28 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:	1258311
Bug Blocks:

Description Krutika Dhananjay 2015-08-31 10:20:40 UTC

+++ This bug was initially created as a clone of Bug #1258311 +++

Description of problem:

Printing the total write size in the writev wind path of trace translator is useful for debugging issues in sharding.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

--- Additional comment from Anand Avati on 2015-08-31 00:49:21 EDT ---

REVIEW: http://review.gluster.org/12053 (debug/trace: Print total write size in trace_writev) posted (#1) for review on master by Krutika Dhananjay (kdhananj)

--- Additional comment from Anand Avati on 2015-08-31 06:11:09 EDT ---

COMMIT: http://review.gluster.org/12053 committed in master by Vijay Bellur (vbellur) 
------
commit fb8c9b38d8c42ecaf17df6e28c2a97d2cf13fb14
Author: Krutika Dhananjay <kdhananj>
Date:   Mon Aug 31 09:56:02 2015 +0530

    debug/trace: Print total write size in trace_writev
    
    This is some information I find useful while debugging issues
    in shard translator.
    
    Change-Id: Ic35c34c2f52d27b3617fc722dabe558de2056b67
    BUG: 1258311
    Signed-off-by: Krutika Dhananjay <kdhananj>
    Reviewed-on: http://review.gluster.org/12053
    Reviewed-by: Pranith Kumar Karampuri <pkarampu>
    Tested-by: Gluster Build System <jenkins.com>
    Tested-by: NetBSD Build System <jenkins.org>
    Reviewed-by: Vijay Bellur <vbellur>

Comment 1 Anand Avati 2015-08-31 10:38:21 UTC

REVIEW: http://review.gluster.org/12065 (debug/trace: Print total write size in trace_writev) posted (#1) for review on release-3.7 by Krutika Dhananjay (kdhananj)

Comment 2 Anand Avati 2015-09-01 05:57:14 UTC

COMMIT: http://review.gluster.org/12065 committed in release-3.7 by Pranith Kumar Karampuri (pkarampu) 
------
commit b60f931e8e2479d9a93e568b358feb24f52a864b
Author: Krutika Dhananjay <kdhananj>
Date:   Mon Aug 31 09:56:02 2015 +0530

    debug/trace: Print total write size in trace_writev
    
            Backport of: http://review.gluster.org/12053
    
    This is some information I find useful while debugging issues
    in shard translator.
    
    Change-Id: Ia33f656741750b4d5306599ea71ba1dc85bf311d
    BUG: 1258411
    Signed-off-by: Krutika Dhananjay <kdhananj>
    Reviewed-on: http://review.gluster.org/12065
    Reviewed-by: Pranith Kumar Karampuri <pkarampu>
    Tested-by: NetBSD Build System <jenkins.org>
    Tested-by: Gluster Build System <jenkins.com>

Comment 3 Pranith Kumar K 2015-10-14 10:30:28 UTC

This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-glusterfs-3.7.5, please open a new bug report.

glusterfs-glusterfs-3.7.5 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] http://www.gluster.org/pipermail/gluster-users/2015-October/023968.html
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user

Comment 4 Pranith Kumar K 2015-10-14 10:38:51 UTC

This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.7.5, please open a new bug report.

glusterfs-3.7.5 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] http://www.gluster.org/pipermail/gluster-users/2015-October/023968.html
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user