Bug 1374153

+++ This bug was initially created as a clone of Bug #1364420 +++

Description of problem:
If History changelogs backlog to be processed is more then Geo-rep takes lot of time to reach to current state because of rsync retries.

Issue and possible solution is discussed in upstream
http://www.gluster.org/pipermail/gluster-devel/2016-August/050372.html

--- Additional comment from Aravinda VK on 2016-08-08 09:00:13 EDT ---



--- Additional comment from Vijay Bellur on 2016-08-08 09:01:47 EDT ---

REVIEW: http://review.gluster.org/15110 (geo-rep: Post process Data and Meta Changelogs) posted (#1) for review on master by Aravinda VK (avishwan)

--- Additional comment from Vijay Bellur on 2016-08-10 10:10:05 EDT ---

REVIEW: http://review.gluster.org/15110 (geo-rep: Post process Data and Meta Changelogs) posted (#2) for review on master by Aravinda VK (avishwan)

--- Additional comment from Vijay Bellur on 2016-08-11 05:03:28 EDT ---

REVIEW: http://review.gluster.org/15110 (geo-rep: Post process Data and Meta Changelogs) posted (#3) for review on master by Aravinda VK (avishwan)

--- Additional comment from Vijay Bellur on 2016-08-11 05:54:40 EDT ---

REVIEW: http://review.gluster.org/15110 (geo-rep: Post process Data and Meta Changelogs) posted (#4) for review on master by Aravinda VK (avishwan)

--- Additional comment from Vijay Bellur on 2016-08-18 10:56:49 EDT ---

REVIEW: http://review.gluster.org/15110 (geo-rep: Post process Data and Meta Changelogs) posted (#5) for review on master by Aravinda VK (avishwan)

--- Additional comment from Vijay Bellur on 2016-08-20 09:53:37 EDT ---

REVIEW: http://review.gluster.org/15110 (geo-rep: Post process Data and Meta Changelogs) posted (#6) for review on master by Aravinda VK (avishwan)

--- Additional comment from Vijay Bellur on 2016-08-20 12:05:27 EDT ---

REVIEW: http://review.gluster.org/15110 (geo-rep: Post process Data and Meta Changelogs) posted (#7) for review on master by Aravinda VK (avishwan)

--- Additional comment from Worker Ant on 2016-08-24 01:48:06 EDT ---

REVIEW: http://review.gluster.org/15110 (geo-rep: Post process Data and Meta Changelogs) posted (#8) for review on master by Aravinda VK (avishwan)

--- Additional comment from Worker Ant on 2016-08-24 12:55:24 EDT ---

REVIEW: http://review.gluster.org/15110 (geo-rep: Post process Data and Meta Changelogs) posted (#9) for review on master by Aravinda VK (avishwan)

--- Additional comment from Worker Ant on 2016-08-25 08:06:27 EDT ---

REVIEW: http://review.gluster.org/15110 (geo-rep: Post process Data and Meta Changelogs) posted (#10) for review on master by Aravinda VK (avishwan)

--- Additional comment from Worker Ant on 2016-08-26 02:06:54 EDT ---

REVIEW: http://review.gluster.org/15110 (geo-rep: Post process Data and Meta Changelogs) posted (#11) for review on master by Aravinda VK (avishwan)

--- Additional comment from Worker Ant on 2016-08-26 13:46:03 EDT ---

COMMIT: http://review.gluster.org/15110 committed in master by Aravinda VK (avishwan) 
------
commit 6c283f107b646405936520e2549510115bf2ef64
Author: Aravinda VK <avishwan>
Date:   Mon Aug 8 17:02:37 2016 +0530

    geo-rep: Post process Data and Meta Changelogs
    
    With this patch, Data and Meta GFIDs are post processed. If Changelog has
    UNLINK entry then remove from Data and Meta GFIDs list(If stat on GFID is
    ENOENT in Master).
    
    While processing Changelogs,
    
    - Collect all the data and meta operations in a temporary database
    - Delete all Data and Meta GFIDs which are already unlinked as per Changelogs
      (unlink only if stat on GFID is ENOENT)
    - Process all Entry operations as usual
    - Process data and meta operations in batch(Fetch from Db in batch)
    - Data sync is again batched based on number of changelogs(Default 1day
      changelogs). Once the sync is complete, Update last Changelog's time as last_synced
      time as usual.
    
    Additionally maintain entry_stime on Brick root, ignore Entry ops if changelog
    suffix time is less than entry_stime. If data stime is more than entry_stime,
    this can happen only when passive worker updates stime by itself by getting
    mount point stime. Use entry_stime = data_stime in this case.
    
    New configurations:
    
    max-rsync-retries - Default Value is 10
    max-data-changelogs-in-batch - Max number of changelogs to be considered in a
    batch for syncing. Default value is 5760(4 changelogs per min * 60 min *
    24 hours)
    max-history-changelogs-in-batch - Max number of history changelogs to be
    processed at once. Default value 86400(4 changelogs per min * 60 min * 24
    hours * 15 days)
    
    BUG: 1364420
    Change-Id: I7b665895bf4806035c2a8573d361257cbadbea17
    Signed-off-by: Aravinda VK <avishwan>
    Reviewed-on: http://review.gluster.org/15110
    Smoke: Gluster Build System <jenkins.org>
    NetBSD-regression: NetBSD Build System <jenkins.org>
    Reviewed-by: Kotresh HR <khiremat>
    CentOS-regression: Gluster Build System <jenkins.org>

--- Additional comment from Worker Ant on 2016-08-31 06:12:11 EDT ---

REVIEW: http://review.gluster.org/15371 (geo-rep: Fix History post process) posted (#1) for review on master by Aravinda VK (avishwan)

--- Additional comment from Aravinda VK on 2016-08-31 07:41:50 EDT ---

Performance not gaining much as expected. Moving back to post to send fix to remove db changes.

--- Additional comment from Worker Ant on 2016-09-01 02:04:52 EDT ---

REVIEW: http://review.gluster.org/15371 (geo-rep: Fix History post process) posted (#2) for review on master by Aravinda VK (avishwan)

--- Additional comment from Worker Ant on 2016-09-05 01:54:20 EDT ---

REVIEW: http://review.gluster.org/15371 (geo-rep: Fix History post process) posted (#3) for review on master by Aravinda VK (avishwan)

--- Additional comment from Worker Ant on 2016-09-08 02:11:22 EDT ---

COMMIT: http://review.gluster.org/15371 committed in master by Aravinda VK (avishwan) 
------
commit 5de500cd0116796ff797099c60d33258bd48ce3c
Author: Aravinda VK <avishwan>
Date:   Wed Aug 31 11:53:06 2016 +0530

    geo-rep: Fix History post process
    
    This patch removes changelogsdb part of post processing since
    not got much performance advantage as expected.
    
    Entry stime and other logging improvements retained.
    
    BUG: 1364420
    Change-Id: Ib99d23f09d96c14bc28225b47d9134260f5551bf
    Signed-off-by: Aravinda VK <avishwan>
    Reviewed-on: http://review.gluster.org/15371
    NetBSD-regression: NetBSD Build System <jenkins.org>
    CentOS-regression: Gluster Build System <jenkins.org>
    Reviewed-by: Kotresh HR <khiremat>
    Smoke: Gluster Build System <jenkins.org>