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

[bugzilla at redhat.com]

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



--- Comment #18 from Vijay Bellur <vbellur at redhat.com> ---
COMMIT: http://review.gluster.org/12427 committed in release-3.7 by Venky
Shankar (vshankar at redhat.com) 
------
commit 86b6d13e42c2e0de92a2a2099644fbb75308dd12
Author: Saravanakumar Arumugam <sarumuga at redhat.com>
Date:   Fri Oct 9 20:29:30 2015 +0530

    geo-rep: Add data operation if mknod with tier attribute

    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 is addressed here in this patch)

    So, If tier-gfid linkto is set, we need to record the corresponding
    MKNOD. Earlier this was avoided as it was set as INTERNAL fop.
    (This changelog related changes are addressed in the patch:
     - http://review.gluster.org/12417)

    Change-Id: I2fa84cfa2b0f86506c3d15d484138ab9651e4f83
    BUG: 1275173
    Signed-off-by: Saravanakumar Arumugam <sarumuga at redhat.com>
    Reviewed-on: http://review.gluster.org/12326
    Tested-by: NetBSD Build System <jenkins at build.gluster.org>
    Tested-by: Gluster Build System <jenkins at build.gluster.com>
    Reviewed-by: Kotresh HR <khiremat at redhat.com>
    Reviewed-by: Aravinda VK <avishwan at redhat.com>
    (cherry picked from commit ffc39c9d8807464b5c78959bc43dc12b22f5a37b)
    Reviewed-on: http://review.gluster.org/12427
    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.