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

GoXDCR should HELO to the target memcached

    XMLWordPrintable

Details

    • Bug
    • Resolution: Fixed
    • Major
    • 4.6.2, 5.0.0
    • 4.0.0, 4.1.0, 4.1.1, 4.1.2, 4.5.0, 4.5.1
    • XDCR
    • Untriaged
    • Unknown

    Description

      Currently GoXDCR does not identify itself to the target memcached. This makes it very difficult to debug issues where the cluster is receiving XDCR.

      For example, the Java SDK will HELO as follows:

      2017-01-27T13:45:03.313000Z NOTICE 56: HELO [couchbase-java-client/2.3.2 (git: 2.3.2, core: 1.3.2) (Mac OS X/10.12.1 x86_64; Java HotSpot(TM) 64-Bit Server VM 1.8.0_51-b16)] TCP NODELAY [ 127.0.0.1:62424 - 127.0.0.1:11210 ]
      2017-01-27T13:49:25.073254Z NOTICE 56: HELO [couchbase-java-client/2.4.1 (git: 2.4.1, core: 1.4.1) (Mac OS X/10.12.1 x86_64; Java HotSpot(TM) 64-Bit Server VM 1.8.0_51-b16)] TCP NODELAY [ 127.0.0.1:62809 - 127.0.0.1:11210 ]
      

      Obviously, not all of the same information would be relevant for GoXDCR. What would be useful is:

      • The remote cluster's UUID.
      • The remote cluster's version.
      • The remote cluster's replication UUID.
      • Any other identifying info that can reasonably be added.

      Attachments

        Issue Links

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

          Activity

            People

              arunkumar Arunkumar Senthilnathan (Inactive)
              James Flather James Flather (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Gerrit Reviews

                  There are no open Gerrit changes

                  PagerDuty