Uploaded image for project: 'Couchbase Server'
  1. Couchbase Server
  2. MB-6586

Replication rate may drop when the XDCR replication queue size becomes less than 500k items


    • Type: Bug
    • Status: Closed
    • Priority: Critical
    • Resolution: Fixed
    • Affects Version/s: 2.0
    • Fix Version/s: 2.0-beta-2
    • Component/s: XDCR
    • Security Level: Public


      The replicator has a logic that if there are less than 500 items int the queue it will wait a bit (which maybe is too much) until more items shows up.
      This is why the replication rate when the queue is about 600K and less is dropping.

      It seems that when there are 1M items in the queue and more the replication rate is still 5-10K even if there is load on the destination.

      We need to find some solution for that because that logic means that the closer the destination gets to the source, the lower the replication rate is (because there are less items on the XDCR replication queue per vbucket).

      At least the good news is that the front load on the source does not have major impact on the destination.

      Damien is looking at the code in question: I don't see the where the batch size would cause this slowdown. I believe this is a problem in ep-engine where it gets into a state where waking the flusher doesn't work for some reason, so it it must wait for it wake itself.

      I'm going to add some code to see how long we wait for full commits to happen, vs how long we spend doing the other replication work.


        Error rendering 'com.meetme.plugins.jira.gerrit-plugin:gerritreviewsmodule'. Please contact your JIRA administrators.



            • Assignee:
              junyi Junyi Xie (Inactive)
              ketaki Ketaki Gangal
            • Votes:
              0 Vote for this issue
              1 Start watching this issue


              • Created:

                Gerrit Reviews Side Panel

                Error rendering 'com.meetme.plugins.jira.gerrit-plugin:gerrit-reviews-side-panel'. Please contact your JIRA administrators.