[DOCS-14851] [Server] DNS Seed List Connection Format section has missing information for sharded cluster Created: 05/Oct/21 Updated: 20/Nov/23 Resolved: 16/Nov/23 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual, Server |
| Affects Version/s: | None |
| Fix Version/s: | Server_Docs_20231120 |
| Type: | Task | Priority: | Minor - P4 |
| Reporter: | Sergei Timoshtshuk | Assignee: | Sarah Simpers |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | bug, bugfix, reopened, replication, server-docs-bug-bash, sharding | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 11 weeks, 6 days ago |
| Story Points: | 2 |
| Description |
|
https://docs.mongodb.com/manual/reference/connection-string/#dns-seed-list-connection-format "DNS Seed List Connection Format" has missing tab switch between replica set and sharded cluster and describes it only for mongod instances, which confuses customers that this configuration is not available for mongos.
|
| Comments |
| Comment by Sarah Simpers [ 16/Nov/23 ] |
|
I confirmed that this was fixed when I revamped the page. You can now use tabs to see SRV connection string for replica set vs sharded, and can select mongosh from the drop-down to see the mongosh string versus the driver strings: https://www.mongodb.com/docs/manual/reference/connection-string/#find-your-self-hosted-deployment-s-connection-string Since this is fixed, I will close this ticket. Thanks! |
| Comment by Sarah Simpers [ 16/Nov/23 ] |
|
I believe this issue was resolved when I revamped this page for the Atlas Top 250 effort, but I will confirm before closing. |
| Comment by Sarah Olson [ 02/Nov/22 ] |
|
Thanks for the confirm, spencer.brown@mongodb.com. |
| Comment by Spencer Brown [ 31/Oct/22 ] |
|
This documentation issue still needs to be fixed, need to describe the DNS seed list format for sharded clusters (list of mongos hostnames/ports). |
| Comment by Education Bot [ 31/Oct/22 ] |
|
Hello! This ticket has been closed due to inactivity. If you believe this ticket is still important, please reopen it and leave a comment to explain why. Thank you! |