[Bugs] [Bug 1261146] Legacy files pre-existing tier attach must be promoted

[bugzilla at redhat.com]

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



--- Comment #3 from Vijay Bellur <vbellur at redhat.com> ---
COMMIT: http://review.gluster.org/12331 committed in release-3.7 by Dan
Lambright (dlambrig at redhat.com) 
------
commit 2def6bbfc72f9dd7ae6a16befdaf45ac1076b648
Author: Joseph Fernandes <josferna at redhat.com>
Date:   Tue Aug 4 20:38:06 2015 +0530

    tier/ctr: CTR DB named lookup heal of cold tier during attach tier

    Heal hardlink in the db for already existing data in the cold
    tier during attach tier. i.e during fix layout do lookup to files
    in the cold tier.

    CTR xlator on the  brick/server side does db update/insert of the hardlink
on a namelookup.
    Currently the namedlookup is done synchronous to the fixlayout that is
    triggered by attach tier. This is not performant, adding more time to
    fixlayout. The performant approach is record the hardlinks on a compressed
    datastore and then do the namelookup asynchronously later, giving the ctr
db
    eventual consistency

    master patch : http://review.gluster.org/#/c/11828/

    >>Change-Id: I4ffc337fffe7d447804786851a9183a51b5044a9
    >>BUG: 1252586
    >>Signed-off-by: Joseph Fernandes <josferna at redhat.com>
    >>Reviewed-on: http://review.gluster.org/11828
    >>Tested-by: Gluster Build System <jenkins at build.gluster.com>
    >>Reviewed-by: Dan Lambright <dlambrig at redhat.com>
    >>Tested-by: Dan Lambright <dlambrig at redhat.com>
    Signed-off-by: Joseph Fernandes <josferna at redhat.com>

    Change-Id: I61b185a54ae4e8c1d82804b95a278bfbea870987
    BUG: 1261146
    Reviewed-on: http://review.gluster.org/12331
    Tested-by: NetBSD Build System <jenkins at build.gluster.org>
    Tested-by: Gluster Build System <jenkins at build.gluster.com>
    Reviewed-by: Dan Lambright <dlambrig at redhat.com>
    Tested-by: Dan Lambright <dlambrig 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.