Bug 1561732

Summary:	Rebalance failures on a dispersed volume with lookup-optimize enabled
Product:	[Community] GlusterFS	Reporter:	Xavi Hernandez <jahernan>
Component:	disperse	Assignee:	Xavi Hernandez <jahernan>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	3.10	CC:	bugs
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-3.10.12	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1561406	Environment:
Last Closed:	2018-05-07 15:05:04 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:	1561406
Bug Blocks:

Description Xavi Hernandez 2018-03-28 18:44:27 UTC

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

Description of problem:

When rebalance is executed after adding a brick (or some other operation that changes the layout) on a dispersed volume with lookup-optimize enabled, some files are not migrated to the right brick.

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


How reproducible:

Always

Steps to Reproduce:
1. Create a disperse volume
2. Enable lookup-optimize
3. Create some files
4. Add new bricks
5. Run rebalance

Actual results:

Some files are not migrated

Expected results:

All files should be migrated

Additional info:

There's a bug in EC that causes the request for trusted.glusterfs.list-node-uuids xattr to be only processed in one subvolume. This causes that the resulting list only contains one of the UUIDs and all the other are set to the null uuid, as if they were down.

Comment 1 Worker Ant 2018-03-28 18:46:16 UTC

REVIEW: https://review.gluster.org/19792 (cluster/ec: send list-node-uuids request to all subvolumes) posted (#1) for review on release-3.10 by Xavi Hernandez

Comment 2 Worker Ant 2018-04-05 15:36:15 UTC

COMMIT: https://review.gluster.org/19792 committed in release-3.10 by "Shyamsundar Ranganathan" <srangana> with a commit message- cluster/ec: send list-node-uuids request to all subvolumes

The xattr trusted.glusterfs.list-node-uuids was only sent to a single
subvolume. This was returning null uuids from the other subvolumes as
if they were down.

This fix forces that xattr to be requested from all subvolumes.

Backport of:
> BUG: 1561406

Change-Id: If62eb39a6857258923ba625e153d4ad79018ea2f
BUG: 1561732
Signed-off-by: Xavi Hernandez <xhernandez>

Comment 3 Shyamsundar 2018-05-07 15:05:04 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.10.12, please open a new bug report.

glusterfs-3.10.12 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-April/000095.html
[2] https://www.gluster.org/pipermail/gluster-users/