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

CAPI (v1) XDCR causes very high CPU usage

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 4.0.0
    • 4.1.0
    • XDCR
    • Security Level: Public
    • None
    • Untriaged
    • Yes

    Description

      This appears to be a regression from 3.1 (per QE team).

      Simple steps are to setup a uni-directional XDCR using CAPI (v1) and observe that the CPU usage goes to 100%. A semi-workaround is to reduce the number of replicators to 2, but that still results in 60-70% CPU usage.

      Attachments

        No reviews matched the request. Check your Options in the drop-down menu of this sections header.

        Activity

          envitraux envitraux added a comment -

          I just upgrade to Version: 4.0.0-4051 Community Edition (build-4051) as well and I am also seeing goxdcr is using a lot of CPU on the nodes.

          To mitigate the problem slightly I have set

          XDCR Source Nozzles per Node: 2
          XDCR Target Nozzles per Node: 2

          envitraux envitraux added a comment - I just upgrade to Version: 4.0.0-4051 Community Edition (build-4051) as well and I am also seeing goxdcr is using a lot of CPU on the nodes. To mitigate the problem slightly I have set XDCR Source Nozzles per Node: 2 XDCR Target Nozzles per Node: 2

          Hi Val Entin, Envitraux,

          Yes this is known issue in Couchbase Server 4.0 + ElasticSearch plugin and reported in release notes - http://developer.couchbase.com/documentation/server/4.0/release-notes/relnotes-40-ga.html

          Summary: Running the Elasticsearch connector may result in a high CPU usage.

          Workaround: In a development environment, limit the XDCR replicators to 2 with 2 source and 2 target nozzles per node to reduce the CPU overhead.

          anil Anil Kumar (Inactive) added a comment - Hi Val Entin, Envitraux, Yes this is known issue in Couchbase Server 4.0 + ElasticSearch plugin and reported in release notes - http://developer.couchbase.com/documentation/server/4.0/release-notes/relnotes-40-ga.html Summary: Running the Elasticsearch connector may result in a high CPU usage. Workaround: In a development environment, limit the XDCR replicators to 2 with 2 source and 2 target nozzles per node to reduce the CPU overhead.
          Val Entin2 Val Entin2 added a comment -

          Thanks for your answers (and sorry to haven't read the release note).
          Done that on dev environment it's working like a charm thanks.

          Val Entin2 Val Entin2 added a comment - Thanks for your answers (and sorry to haven't read the release note). Done that on dev environment it's working like a charm thanks.

          Arun,

          Can you automate this use case ?

          -Thanks
          Ritesh

          ritesh.motlani Ritesh Motlani (Inactive) added a comment - Arun, Can you automate this use case ? -Thanks Ritesh

          Ritesh,

          All CAPI test requests should be assigned to Elastic Search connector owner (Subhashini). See my comment on CBQE-3456.

          Thanks
          Aruna

          apiravi Aruna Piravi (Inactive) added a comment - Ritesh, All CAPI test requests should be assigned to Elastic Search connector owner (Subhashini). See my comment on CBQE-3456. Thanks Aruna

          People

            arunkumar Arunkumar Senthilnathan (Inactive)
            perry Perry Krug
            Votes:
            0 Vote for this issue
            Watchers:
            14 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Gerrit Reviews

                There are no open Gerrit changes

                PagerDuty