Bug 1286070

Summary:	DHT - rebalance - Once User has run rebalance with 'start force' option and after successful completion of it, nothing got changed on volume.re run of rebalance is migrating files
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Susant Kumar Palai <spalai>
Component:	distribute	Assignee:	Nithya Balachandran <nbalacha>
Status:	CLOSED CURRENTRELEASE	QA Contact:	storage-qa-internal <storage-qa-internal>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	rhgs-3.1	CC:	kaushal, kramdoss, mzywusko, nbalacha, racpatel, rgowdapp, rhs-bugs, rwheeler, smohan, spalai, tdesala, vbellur
Target Milestone:	---	Keywords:	ZStream
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:	dht-rebalance, dht-fixed
Fixed In Version:	3.7.9-10	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	956208	Environment:
Last Closed:	2016-09-09 10:04:56 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:	956208
Bug Blocks:

Comment 2 Raghavendra G 2016-06-28 12:21:13 UTC

In the version specified, fix-layout changed the layout blindly even though the layout is spread on all the bricks and it doesn't has any anomalies (holes/overlaps). So, the second run of rebalance might've changed the layout and hence file migration. However this behavior is fixed in 3.1. It needs to retested.

Comment 4 Prasad Desala 2016-09-09 04:44:41 UTC

This issue is not seen on gluster build: 3.7.9-10.el7rhgs.x86_64.

Here are the steps that were followed,

1. Created a Distributed replica volume and started it.
2. Fuse Mounted the volume from the client-1 and created files and directories.
4. Added few bricks and started rebalance for that volume with force option.
5. Rebalance completed successfully as expected.
6. Without making any changes to I/O on mount point again started rebalance for that volume with force option.

Rebalance was completed and no files were rebalanced/migrated as there were no changes to I/O on mount point which is expected.

Hence, moving this bug state to Verified.

Comment 5 Nithya Balachandran 2016-09-09 10:04:56 UTC

Thanks Prasad. 

Closing this BZ as per comment#4.