[Bugs] [Bug 1219608] IO touched a file undergoing migration fails for tiered volumes

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1219608



--- Comment #1 from Anand Avati <aavati at redhat.com> ---
COMMIT: http://review.gluster.org/10654 committed in release-3.7 by Vijay
Bellur (vbellur at redhat.com) 
------
commit eee703473f17e3784e15dba291cc3df00fde9f96
Author: Dan Lambright <dlambrig at redhat.com>
Date:   Thu May 7 14:59:51 2015 -0400

    guster/dht: tiered volumes may not allow access to files undergoing
migration

    This is a backport of fix 10324 to Gluster 3.7.

    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.

    > http://review.gluster.org/#/c/10324/
    > Change-Id: Ia4acb0035ff1da15f6a8f9ed54f43c76e8b98f5f
    > BUG: 1214048
    > Signed-off-by: Dan Lambright <dlambrig at redhat.com>
    > Signed-off-by: root <root at gprfs018.sbu.lab.eng.bos.redhat.com>
    > Signed-off-by: Dan Lambright <dlambrig at redhat.com>
    > Reviewed-on: http://review.gluster.org/10324
    > Tested-by: NetBSD Build System
    > Tested-by: Gluster Build System <jenkins at build.gluster.com>
    > Reviewed-by: Raghavendra G <rgowdapp at redhat.com>
    > Tested-by: Raghavendra G <rgowdapp at redhat.com>
    > Signed-off-by: Dan Lambright <dlambrig at redhat.com>

    Change-Id: Ia4acb0035ff1da15f6a8f9ed54f43c76e8b98f5f
    BUG: 1219608
    Signed-off-by: Dan Lambright <dlambrig at redhat.com>
    Reviewed-on: http://review.gluster.org/10654
    Tested-by: Gluster Build System <jenkins at build.gluster.com>
    Tested-by: NetBSD Build System
    Reviewed-by: Joseph Fernandes
    Reviewed-by: Vijay Bellur <vbellur at redhat.com>

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
You are the assignee for the bug.