Fixed
Pinned fields
Click on the next to a field label to start pinning.
Details
Assignee
Ayush NayyarAyush NayyarReporter
Neil HuangNeil HuangIssue Impact
externalStory Points
1Priority
MajorInstabug
Open Instabug
Details
Details
Assignee
Ayush Nayyar
Ayush NayyarReporter
Neil Huang
Neil HuangIssue Impact
external
Story Points
1
Priority
Instabug
Open Instabug
PagerDuty
PagerDuty
PagerDuty
Sentry
Sentry
Sentry
Zendesk Support
Zendesk Support
Zendesk Support
Created June 6, 2023 at 5:43 PM
Updated March 21, 2025 at 7:42 PM
Resolved June 23, 2023 at 5:23 PM
Discussed in AV-42129 – Capella would like an XDCR source/target connection pre-check feature for XDCR out of Capella instances to self-managed clusters. A feature like this would be best to do in the Server, and it would also be useful for all customers (since all customers have to deal with networking, firewalls, etc).
So, a connection pre-check 1) as an option that can be done when a remote is added and 2) as something that's done automatically when starting the replication.
Side note: mentioned that Support (See duplicate ) has been wanting a feature like this as well since 2016, as XDCR source/target connection issues are not uncommon.
NH: 7.2.1 is probably a good vehicle needed for Capella intergration work.
Issue
Resolution
XDCR could fail due to multiple connection issues. For example, DNS issues or firewalls. For a number of databases, it was a difficult task to manually check every node to determine where the connection issue was. For multiple nodes in a database and in the target database, debugging the issue required many connection checks.
A connection pre-check feature has been added to XDCR which ensures all connections from source nodes to target nodes are valid. Credentials are now also checked.