[Bugs] [Bug 1275173] geo-replication: [RFE] Geo-replication + Tiering

[bugzilla at redhat.com]

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



--- Comment #17 from Vijay Bellur <vbellur at redhat.com> ---
COMMIT: http://review.gluster.org/12428 committed in release-3.7 by Venky
Shankar (vshankar at redhat.com) 
------
commit 7598d5e1466971e02823a9f663059f6e18b8361a
Author: Saravanakumar Arumugam <sarumuga at redhat.com>
Date:   Fri Oct 23 11:57:42 2015 +0530

    features/changelog: record mknod if tier-dht linkto is set

    This is a series of patches which aims to fix geo-replication
    in a Tiering Volume.

    Problem:
    Consider, a file is placed in volume initially and then hot tier is
    attached. During any operation on the file, due to lookup a linkto
    file is created in hot tier.

    Now, any namespace operation carried out on the file is recorded in
    both cold and hot tier.
    There is a room for races when both changelogs are replayed.

    Solution:
    So, We are going to replay (namespace related)operations
    only in the hot tier.

    Why?
    a. If the file is directly placed in Hot tier, all fops will be
    recorded in HOT tier.

    b. If  the file is already present in Cold tier, and if any fop is
    carried out, it creates linkto file in Hot tier.
    Now, operations like UNLINK, RENAME are captured in Hot tier(by means of
linkto file).

    This way, we can get both tier's operation in HOT tier itself.

    But, We may miss initial Data sync immediately after creating the
    file as it is only recording MKNOD. So, if MKNOD encountered
    with sticky bit set, queue DATA operation for the corresponding gfid.
    ( This geo-rep related changes are addressed in this patch:
http://review.gluster.org/12326/ )

    So, If tier-dht linkto is set, we need to record the corresponding
    MKNOD. Earlier this was avoided as it was set as INTERNAL fop.
    (This is addressed here in this patch)

    Change-Id: I25514fe3e25f68592a8d6361507f8c8a4fcb70b1
    BUG: 1275173
    Reviewed-on: http://review.gluster.org/12417
    Signed-off-by: Saravanakumar Arumugam <sarumuga at redhat.com>
    Reviewed-on: http://review.gluster.org/12428
    Tested-by: Gluster Build System <jenkins at build.gluster.com>
    Tested-by: NetBSD Build System <jenkins at build.gluster.org>
    Reviewed-by: Venky Shankar <vshankar at redhat.com>

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