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

XDCR should use 11210/CCCP/Optimized Connection Management for Remote Cluster Topology

    XMLWordPrintable

Details

    • Improvement
    • Resolution: Done
    • Major
    • feature-backlog
    • 4.0.0, 4.1.0, 4.1.1, 4.1.2, 4.5.0, 4.5.1, 4.6.0, 4.6.1, 4.6.2, 5.0.0
    • XDCR

    Description

      Currently XDCR makes a variety of calls to 8091 for various topology checks on the remote cluster. Each source node does this individually to the same remote node, essentially DDoSing that node for larger clusters.

      SDKs have already resolved this issue by using CCCP/Optimized Connection Management - XDCR should do the same.

      I suspect this would be easier to pick up as part of MB-22712. Let me know if you think there are any edge cases where XDCR needs to do more than a standard client does.

      Attachments

        Issue Links

          finishs with

          Bug - A problem which impairs or prevents the functions of the product. MB-44823 XDCR hitting pools/nodes endpoint should be coordinated

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MB-45983 XDCR - coordinate topologyChangeDetector effort to lessen load on ns_server

          • Major - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MB-46925 XDCR - large memory footprint for pipeline supervisor with large number of replications

          • Major - Major loss of function.
          • Closed

          Improvement - An improvement or enhancement to an existing feature or task. MB-25918 RemoteClusterService Improvement Redesign

          • Critical - Crashes, loss of data, severe memory leak.
          • Resolved
          relates to

          Improvement - An improvement or enhancement to an existing feature or task. MB-22712 Use Official go-SDK (gocb) for XDCR

          • Critical - Crashes, loss of data, severe memory leak.
          • Open
          No reviews matched the request. Check your Options in the drop-down menu of this sections header.

          Activity

            People

              James Flather James Flather (Inactive)
              James Flather James Flather (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Gerrit Reviews

                  There are no open Gerrit changes

                  PagerDuty