Description
When XDCR ref is being created with full encryption, by default XDCR tries 8091, then get the port, and then try 18091 (default) serially.
This could take some time and we can prob just try 18091 in parallel when XDCR pings 8091 in the beginning. If 18091 handshake with TLS succeeds, great. We can move on more quickly.
Attachments
Issue Links
- relates to
-
MB-40951 Can't XDCR from non-cloud cluster to Cloud cluster
- Closed