Bug 1318196

Summary:	DHT-rebalance: rebalance status shows failed when replica pair bricks are brought down in distrep volume while re-name of files going on
Product:	[Community] GlusterFS	Reporter:	Susant Kumar Palai <spalai>
Component:	distribute	Assignee:	Susant Kumar Palai <spalai>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	high	Docs Contact:
Priority:	high
Version:	3.7.9	CC:	annair, asriram, asrivast, bugs, byarlaga, nbalacha, rhs-bugs, sankarshan, smohan, trao
Target Milestone:	---	Keywords:	ZStream
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	glusterfs-3.7.11	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1257076	Environment:
Last Closed:	2016-04-19 07:12:36 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:	1237059, 1257076
Bug Blocks:	1216951

Comment 1 Vijay Bellur 2016-03-16 09:19:53 UTC

REVIEW: http://review.gluster.org/13749 (cluster/dht/rebalance: rebalance failure handling) posted (#1) for review on release-3.7 by Susant Palai (spalai)

Comment 2 Vijay Bellur 2016-04-04 06:08:43 UTC

REVIEW: http://review.gluster.org/13749 (cluster/dht/rebalance: rebalance failure handling) posted (#2) for review on release-3.7 by Susant Palai (spalai)

Comment 3 Vijay Bellur 2016-04-06 06:34:00 UTC

COMMIT: http://review.gluster.org/13749 committed in release-3.7 by Raghavendra G (rgowdapp) 
------
commit c6d2f61d1aadfe7f93ec0da66b1b23c7f96d09dc
Author: Susant Palai <spalai>
Date:   Wed Aug 26 04:49:29 2015 -0400

    cluster/dht/rebalance: rebalance failure handling
    
    At current state rebalance aborts basically on any failure
    like fix-layout of a directory, readdirp, opendir etc. Unless it is
    not a remove-brick process we can ignore these failures.
    
    Major impact:  Any failure in the gf_defrag_process_dir means there
    are files left unmigrated in the directory.
    
    Fix-layout(setxattr) failure will impact it's child subtree i.e.
    the child subtree will not be rebalanced.
    
    Settle-hash (commit-hash)failure will trigger lookup_everywhere for
    immediate children until the next commit-hash.
    
    Note: Remove-brick opertaion is still sensitive to any kind of failure.
    
    Change-Id: I2f67a490e4e7d06423bb5bc010a1373a74a6af1d
    BUG: 1318196
    Signed-off-by: Susant Palai <spalai>
    Reviewed-on: http://review.gluster.org/12013
    Tested-by: NetBSD Build System <jenkins.org>
    Reviewed-by: Raghavendra G <rgowdapp>
    Signed-off-by: Susant Palai <spalai>
    Reviewed-on: http://review.gluster.org/13749
    Tested-by: N Balachandran <nbalacha>
    NetBSD-regression: NetBSD Build System <jenkins.org>
    CentOS-regression: Gluster Build System <jenkins.com>
    Smoke: Gluster Build System <jenkins.com>

Comment 4 Kaushal 2016-04-19 07:12:36 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.11, please open a new bug report.

glusterfs-3.7.11 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-users/2016-April/026321.html
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user