Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1367305

Summary:	thread CPU saturation limiting throughput on write workloads
Product:	[Community] GlusterFS	Reporter:	Oleksandr Natalenko <oleksandr>
Component:	fuse	Assignee:	Oleksandr Natalenko <oleksandr>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	3.7.14	CC:	bugs
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:	glusterfs-3.7.15	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-09-01 09:21:42 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:

Description Oleksandr Natalenko 2016-08-16 07:40:59 UTC

Backport of https://bugzilla.redhat.com/show_bug.cgi?id=1361678 fix to 3.7.

Comment 1 Vijay Bellur 2016-08-16 07:47:07 UTC

REVIEW: http://review.gluster.org/15168 (cluster/afr: copy loc before passing to syncop) posted (#1) for review on release-3.7 by Oleksandr Natalenko (oleksandr)

Comment 2 Vijay Bellur 2016-08-17 11:44:15 UTC

COMMIT: http://review.gluster.org/15168 committed in release-3.7 by Pranith Kumar Karampuri (pkarampu) 
------
commit 318aacabbc482bcc2e1686988a77ad0bc054837e
Author: Pranith Kumar K <pkarampu>
Date:   Tue Aug 2 15:19:00 2016 +0530

    cluster/afr: copy loc before passing to syncop
    
    Problem:
    When io-threads is enabled on the client side, io-threads destroys the
    call-stub in which the loc is stored as soon as the c-stack unwinds.
    Because afr is creating a syncop with the address of loc passed in
    setxattr by the time syncop tries to access it, io-threads would have
    already freed the call-stub. This will lead to crash.
    
    Fix:
    Copy loc to frame->local and use it's address.
    
    > Reviewed-on: http://review.gluster.org/15070
    > Smoke: Gluster Build System <jenkins.org>
    > CentOS-regression: Gluster Build System <jenkins.org>
    > NetBSD-regression: NetBSD Build System <jenkins.org>
    > Reviewed-by: Ravishankar N <ravishankar>
    
    BUG: 1367305
    Change-Id: I16987e491e24b0b4e3d868a6968e802e47c77f7a
    Signed-off-by: Pranith Kumar K <pkarampu>
    Signed-off-by: Oleksandr Natalenko <oleksandr>
    Reviewed-on: http://review.gluster.org/15168
    Reviewed-by: Ravishankar N <ravishankar>
    Smoke: Gluster Build System <jenkins.org>
    CentOS-regression: Gluster Build System <jenkins.org>
    NetBSD-regression: NetBSD Build System <jenkins.org>

Comment 3 Kaushal 2016-09-01 09:21:42 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.15, please open a new bug report.

glusterfs-3.7.15 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] https://www.gluster.org/pipermail/gluster-devel/2016-September/050714.html
[2] https://www.gluster.org/pipermail/gluster-users/

Comment 4 Kaushal 2016-09-01 09:33:27 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.15, please open a new bug report.

glusterfs-3.7.15 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] https://www.gluster.org/pipermail/gluster-devel/2016-September/050714.html
[2] https://www.gluster.org/pipermail/gluster-users/