[Bugs] [Bug 1200733] [geo-rep]: some of the pre existing files before geo-rep session did not sync to slave

[bugzilla at redhat.com]

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



--- Comment #4 from Anand Avati <aavati at redhat.com> ---
COMMIT: http://review.gluster.org/9855 committed in master by Vijay Bellur
(vbellur at redhat.com) 
------
commit 7d8be3613f7384f5118f26e194fe7c64ea69d11c
Author: Aravinda VK <avishwan at redhat.com>
Date:   Wed Mar 11 13:31:09 2015 +0530

    geo-rep: Do not use xsync_upper_limit for change detection

    Use register time(xsync_upper_limit) only for stime update, do not
    use for change detection.

    Problem 1:
    If a file created before geo-rep, xtime xattr does not exist.
    Geo-rep updates xtime of the file to current time if not exists.
    xtime > upper_limit so geo-rep will not pick those files. Changelog
    either will have SETXATTR, and fails to sync the file.

    Problem 2:
    If a file is created before geo-rep create and updated after
    geo-rep start. xtime of the file is greater than upper limit(geo-rep
    start time/changelog register time). Geo-rep(XSync) will not pick this
    file for syncing. Changelog will have only DATA recorded for that file.
    Geo-rep tries DATA without any ENTRY ops and fails with rsync error.

    BUG: 1200733
    Change-Id: Ie4e8f284db689d2c755ef8e7ecbb658db1c0785f
    Signed-off-by: Aravinda VK <avishwan at redhat.com>
    Reviewed-on: http://review.gluster.org/9855
    Reviewed-by: Kotresh HR <khiremat at redhat.com>
    Reviewed-by: Saravanakumar Arumugam <sarumuga at redhat.com>
    Tested-by: Saravanakumar Arumugam <sarumuga at redhat.com>
    Tested-by: Gluster Build System <jenkins at build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur at redhat.com>

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=yDe2cccahR&a=cc_unsubscribe