Details
-
Bug
-
Resolution: Fixed
-
Major
-
5.5.6, 6.0.3, 6.5.0
-
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
For Gerrit Dashboard: MB-37761 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
123156,2 | MB-37761 - Implemented remote cluster agent address preference - Allow utilities and pipelines to request specific external or internal address when possible - Remote cluster agent is now monitors for user's intention change - Pipeline Manager now checks for remote cluster changes and restart pipelines that require these changes - Raise warning to UI if pipelines restart due to target-side config changes | mad-hatter | goxdcr | Status: MERGED | +2 | +1 |