[DOCS-15527] PL index change in the cross-region cluster Created: 08/Aug/22 Updated: 02/Jun/23 |
|
| Status: | Blocked |
| Project: | Documentation |
| Component/s: | Atlas |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Nika Vestfal-Karidi | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | PrivateLink, connection-string, dns, endpoint | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Atlas, M40 Azure, 4.2.21 |
||
| Issue Links: |
|
||||
| Participants: | |||||
| Days since reply: | 35 weeks, 5 days ago | ||||
| Description |
|
While adding new nodes to the cross-region clusters, Private Endpoint connection string index changes. It can lead to the DNS not being able to find nodes as soon as the connection string is changed. In order to avoid the possible confusion on the Atlas user side, it would be great to be more explicit in the docs about the SRV record name using index 0 in the cross-region case. As mentioned below: Old: mongodb+srv://abc-pl-1.xxxxx.mongodb.net/ It changes the numbering of the nodes. For example under: choose a connection method and regionalized private endpoints for multi-region sharded clusters. |
| Comments |
| Comment by John Williams [ 02/Jun/23 ] |
|
Hi nika.vestfal-karidi@mongodb.com can you provide us with additional guidance on what we need to update in the docs? I reviewed the docs and the linked support cases and it's still not clear. It looks like the examples we have use an index of `0` already. |
| Comment by Will Huang [ 15/Mar/23 ] |
|
Any updates on this? |
| Comment by Nika Vestfal-Karidi [ 22/Feb/23 ] |
|
I will sync with my colleague tomorrow on this and update you. Thank you! |
| Comment by Emet Ozar [ 17/Feb/23 ] |
|
nika.vestfal-karidi@mongodb.com Hello! Just wanted to check in to see if this was something we should still be waiting on? |