REVIEW: http://review.gluster.org/12013 (cluster/dht/rebalance: rebalance failure handling) posted (#1) for review on master by Susant Palai (spalai)
REVIEW: http://review.gluster.org/12013 (cluster/dht/rebalance: rebalance failure handling) posted (#2) for review on master by Susant Palai (spalai)
REVIEW: http://review.gluster.org/12013 (cluster/dht/rebalance: rebalance failure handling) posted (#3) for review on master by Susant Palai (spalai)
REVIEW: http://review.gluster.org/12013 (cluster/dht/rebalance: rebalance failure handling) posted (#4) for review on master by Susant Palai (spalai)
REVIEW: http://review.gluster.org/12013 (cluster/dht/rebalance: rebalance failure handling) posted (#5) for review on master by Susant Palai (spalai)
changing version to mainline in order to retire pre-release. If you know the appropriate, correct version for this bug, please set it.
REVIEW: http://review.gluster.org/12013 (cluster/dht/rebalance: rebalance failure handling) posted (#6) for review on master by Susant Palai (spalai)
COMMIT: http://review.gluster.org/12013 committed in master by Raghavendra G (rgowdapp) ------ commit a53c5c8e322e30b865b7c69aa9558474e033c89a 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: I08ab71909bc832f03cc1517172525376f7aed14a BUG: 1257076 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>
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.8.0, please open a new bug report. glusterfs-3.8.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://blog.gluster.org/2016/06/glusterfs-3-8-released/ [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user