[Bugs] [Bug 1217930] Geo-replication very slow, not able to sync all the files to slave

[bugzilla at redhat.com]

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



--- Comment #3 from Anand Avati <aavati at redhat.com> ---
COMMIT: http://review.gluster.org/10499 committed in release-3.7 by Venky
Shankar (vshankar at redhat.com) 
------
commit 613414e837cb5a09c3adbf2258ad691151f1c7e1
Author: Aravinda VK <avishwan at redhat.com>
Date:   Sat Apr 11 20:03:47 2015 +0530

    geo-rep: Limit number of changelogs to process in batch

    Changelog processing is done in batch, for example if 10 changelogs
    available for processing then process all at once. Collect Entry, Meta
    and Data operations separately, All the entry operations like CREATE,
    MKDIR, MKNOD, LINK, UNLINK will be executed first then rsync will be
    triggered for whole batch. Stime will get updated once the complete
    batch is complete.

    In case of large number of Changelogs in a batch, If geo-rep fails after
    Entry operations, but before rsync then on restart, it again starts from
the
    beginning since stime is not updated. It has to process all the changelogs
    again. While processing same changelogs again, all CREATE will get EEXIST
    since all the files created in previous run. Big hit for performance.

    With this patch, Geo-rep limits number of changelogs per batch based on
    Changelog file size. So that when geo-rep fails it has to retry only last
batch
    changelogs since stime gets updated after each batch.

    BUG: 1217930
    Change-Id: I844448c4cdcce38a3a2e2cca7c9a50db8f5a9062
    Signed-off-by: Aravinda VK <avishwan at redhat.com>
    Reviewed-on: http://review.gluster.org/10202
    Reviewed-by: Kotresh HR <khiremat at redhat.com>
    Reviewed-by: Vijay Bellur <vbellur at redhat.com>
    Reviewed-on: http://review.gluster.org/10499
    Tested-by: Gluster Build System <jenkins at build.gluster.com>
    Tested-by: NetBSD Build System
    Reviewed-by: Venky Shankar <vshankar 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=LfUIuULLyc&a=cc_unsubscribe