Bug 1573119

Summary:	Amends in volume profile option 'gluster-block'
Product:	[Community] GlusterFS	Reporter:	Pranith Kumar K <pkarampu>
Component:	core	Assignee:	Prasanna Kumar Kalever <prasanna.kalever>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	bugs, mpillai, pkarampu, prasanna.kalever, rhinduja, rhs-bugs, sanandpa, sankarshan, storage-qa-internal
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-v4.1.0	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1569951	Environment:
Last Closed:	2018-06-20 18:05:40 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:
Bug Blocks:	1569951

Comment 1 Pranith Kumar K 2018-04-30 08:40:23 UTC

Eager-lock is now giving better performance in block after (https://github.com/gluster/glusterfs/issues/418) so it is advised to use eager-lock on with the newer versions of gluster-block.

Comment 2 Worker Ant 2018-04-30 08:49:23 UTC

REVIEW: https://review.gluster.org/19913 (block-profile: enable cluster.eager-lock in block-profile) posted (#2) for review on master by Pranith Kumar Karampuri

Comment 3 Worker Ant 2018-05-01 12:23:14 UTC

COMMIT: https://review.gluster.org/19913 committed in master by "Niels de Vos" <ndevos> with a commit message- block-profile: enable cluster.eager-lock in block-profile

Eager-lock gave 2.5X perf improvement. On top of that with batching
fix in tcmu-runner and client-io-threads we are seeing close to 3X perf
improvement. But we don't want to include that in the default profile
option but enable it on a case by case basis. So not adding
client-io-threads option.

BUG: 1573119
Fixes: bz#1573119
Change-Id: Ida53c3ef9a041a73b65fdd06158ac082da437206
Signed-off-by: Prasanna Kumar Kalever <prasanna.kalever>

Comment 4 Shyamsundar 2018-06-20 18:05:40 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-v4.1.0, please open a new bug report.

glusterfs-v4.1.0 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://lists.gluster.org/pipermail/announce/2018-June/000102.html
[2] https://www.gluster.org/pipermail/gluster-users/