Details
-
Bug
-
Resolution: Fixed
-
Critical
-
7.1.0, 7.1.1, 7.1.2, 7.2.0, 7.1.3, 7.2.1
-
Untriaged
-
0
-
Unknown
Description
There are a few issues I see.
First one, https://src.couchbase.org/source/xref/7.1.3/goproj/src/github.com/couchbase/goxdcr/utils/utils.go#998 if the call returns an error, the error is not logged or returned. We need to have this information for debugging.
Second one, in the same routine, we look for internal address first, and then replace it with external address. Internal address may be unresolvable. If external is requested, we should use external, and only use internal if alternateAdresses is not available.
Third, we should skip the node if it is not KV.
Issue | Resolution |
When ipv4 only mode was used, and full encryption only had an alternate address configured where the internal address was unresolvable, XDCR resulted in an error when it contacted the target data nodes. | The specific scenario has been fixed so that replication can now proceed. |
Attachments
Issue Links
- is a backport of
-
MB-57364 XDCR - Error parsing memcached ssl port of remote cluster
- Closed