Description of problem: dht/tier/rebalancer: Fix set of client pid for migration. In the patch http://review.gluster.org/#/c/9657 the client pid set by tiering migration was getting over- written in dht_start_rebalance_task(). Just corrected it in dht_setxattr() before calling dht_start_rebalance_task() and removed it from dht_start_rebalance_task(). Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
REVIEW: http://review.gluster.org/10502 (dht/tier/rebalancer: Fix set of client pid for migration) posted (#1) for review on master by Joseph Fernandes (josferna)
REVIEW: http://review.gluster.org/10502 (dht/tier/rebalancer: Fix reset of tiering client pid) posted (#2) for review on master by Joseph Fernandes (josferna)
REVIEW: http://review.gluster.org/10502 (dht/tier/rebalancer: Fix reset of tiering client pid) posted (#3) for review on master by Joseph Fernandes (josferna)
COMMIT: http://review.gluster.org/10502 committed in master by Kaleb KEITHLEY (kkeithle) ------ commit a5fe0f594d41e1a11661d9074bb19e9c2e2c4776 Author: Joseph Fernandes <josferna> Date: Sun May 3 12:41:40 2015 +0530 dht/tier/rebalancer: Fix reset of tiering client pid In the patch http://review.gluster.org/#/c/9657 the client pid set by tiering migration was getting over- written in dht_start_rebalance_task(). Just corrected it in dht_setxattr() before calling dht_start_rebalance_task() and removed it from dht_start_rebalance_task(). Change-Id: I37cfa111f83a4e5d498042575c93799f60b49870 BUG: 1217937 Signed-off-by: Joseph Fernandes <josferna> Reviewed-on: http://review.gluster.org/10502 Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Susant Palai <spalai> Reviewed-by: Dan Lambright <dlambrig>
Fix for this bug is already made in a GlusterFS release. The cloned BZ has details of the fix and the release. Hence closing this mainline BZ.
Fix for this BZ is already present in a GlusterFS release. You can find clone of this BZ, fixed in a GlusterFS release and closed. Hence closing this mainline BZ as well.
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