Fixed
Pinned fields
Click on the next to a field label to start pinning.
Details
Assignee
Ayush NayyarAyush NayyarReporter
Neil HuangNeil HuangIs this a Regression?
UnknownTriage
UntriagedIssue Impact
externalStory Points
0Priority
CriticalInstabug
Open Instabug
Details
Details
Assignee
Ayush Nayyar
Ayush NayyarReporter
Neil Huang
Neil HuangIs this a Regression?
Unknown
Triage
Untriaged
Issue Impact
external
Story Points
0
Priority
Instabug
Open Instabug
PagerDuty
PagerDuty
PagerDuty
Sentry
Sentry
Sentry
Zendesk Support
Zendesk Support
Zendesk Support
Created June 22, 2023 at 7:00 PM
Updated March 21, 2025 at 2:50 AM
Resolved June 23, 2023 at 5:24 PM
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.