Description of problem: If a read IO occurs against a file that has reached rebalance phase 2, we redirect the IO to the destination. For tiered volumes, when we try to reopen the file (on the destination), the lower level DHT receives the open call and fails; it does not have a "cached subvol". Fix it to "teach" the lower level DHT of the new location by sending a locate first in this case.
REVIEW: http://review.gluster.org/10324 (uster/dht: tiered volumes may not allow access to files undergoing migration [WIP]) posted (#1) for review on master by Dan Lambright (dlambrig)
REVIEW: http://review.gluster.org/10324 (guster/dht: tiered volumes may not allow access to files undergoing migration [WIP]) posted (#2) for review on master by Dan Lambright (dlambrig)
REVIEW: http://review.gluster.org/10324 (guster/dht: tiered volumes may not allow access to files undergoing migration) posted (#3) for review on master by Dan Lambright (dlambrig)
REVIEW: http://review.gluster.org/10324 (guster/dht: tiered volumes may not allow access to files undergoing migration) posted (#4) for review on master by Dan Lambright (dlambrig)
REVIEW: http://review.gluster.org/10324 (guster/dht: tiered volumes may not allow access to files undergoing migration) posted (#5) for review on master by Dan Lambright (dlambrig)
COMMIT: http://review.gluster.org/10324 committed in master by Raghavendra G (rgowdapp) ------ commit 8965ac78bfd26e7f45c9579894191817afafa15e Author: Dan Lambright <dlambrig> Date: Wed Apr 29 15:35:56 2015 -0400 guster/dht: tiered volumes may not allow access to files undergoing migration If a read IO occurs against a file that has reached rebalance phase 2, we redirect the IO to the destination. For tiered volumes, when we try to reopen the file (on the destination), the lower level DHT receives the open call and fails; it does not have a "cached subvol". Fix is to "teach" the lower level DHT of the new location by sending a locate before the open. Change-Id: Ia4acb0035ff1da15f6a8f9ed54f43c76e8b98f5f BUG: 1214048 Signed-off-by: Dan Lambright <dlambrig> Signed-off-by: root <root.lab.eng.bos.redhat.com> Signed-off-by: Dan Lambright <dlambrig> Reviewed-on: http://review.gluster.org/10324 Tested-by: NetBSD Build System Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Raghavendra G <rgowdapp> Tested-by: Raghavendra G <rgowdapp>
This change should not be in "ON_QA", the patch posted for this bug is only available in the master branch and not in a release yet. Moving back to MODIFIED until there is an beta release for the next GlusterFS version.
*** Bug 1212084 has been marked as a duplicate of this bug. ***
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