Description
I was trying to test out the scenario of directly XDCR'ing from a self-managed cluster into a Cloud cluster. "in theory" this should work as XDCR acts nearly identically to any other client and therefore should be able to write into a Cloud cluster. "in reality"...not so much
I suspect part of the problem may be handling DNS SRV records which is what Cloud exposes, but even after I tried to bypass that I still got an "unexpected error" from creating the XDCR cluster->cluster connection.
Logs are at:
Attachments
Issue Links
- depends on
-
MB-41166 [XDCR] panic: runtime error: invalid memory address or nil pointer dereference
- Closed
-
MB-41194 XDCR needs to use alternate address when connecting to Couchbase cloud
- Closed
-
MB-41201 XDCR User Intent heuristics is incorrect for SSL use cases
- Closed
- relates to
-
MB-41051 UI Inserting newline character at the end of remote cluster cert
- Closed
-
MB-41043 XDCR setup screens missing spinner
- Closed
-
MB-41041 XDCR UI passing in "null" string for empty fields by default
- Closed
-
MB-41044 XDCR getting SSL ports timeout needs to be shortened
- Closed
-
MB-41074 XDCR DNS SRV not following RFC2782
- Closed
-
MB-41197 XDCR to support retrieve collection manifest over SSL
- Closed
-
MB-37684 XDCR Remote Cluster is not Idempotent due to lack of DNS SRV support
- Closed
-
MB-41052 Try 8091 and 18091 in parallel to improve performance
- Closed
-
MB-41259 XDCR to not tag collection ID 0 when replicating to legacy target cluster
- Closed
-
MB-41230 XDCR services to gracefully handle connecting to non-collection cluster
- Closed