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

[BP 6.5.1] - XDCR does not apply the correct alternate address heuristic

    XMLWordPrintable

Details

    • Bug
    • Resolution: Fixed
    • Major
    • 6.5.1
    • 5.5.6, 6.0.3, 6.5.0
    • XDCR
    • Untriaged
    • No

    Description

      If a remote cluster has an external address set, then when XDCR connects it will always use the external address - see https://github.com/couchbase/goxdcr/blob/e607ce676319355180b1e07a832f2c9b557da0c4/utils/utils.go#L983-L992.

      This is in contrast to the SDKs where they select which address (default vs external) based on the node that you initially connect to.

      XDCR should behave in the same way, as there's no guarantee that XDCR can access the external hostname ports, even if they are set for other clients to access.
      If you initiate an XDCR reference with the external hostname (i.e. it's present in the external address section of the node info), then it should use the external address, otherwise it should use the default address/ports.

      Attachments

        Issue Links

          Activity

            People

              neil.huang Neil Huang
              neil.huang Neil Huang
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                PagerDuty