DOCSP-49054: Connection targets #589
Conversation
✅ Deploy Preview for docs-csharp ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
mcmorisi
requested review from
a team,
JamesKovacs and
papafe
and removed request for
a team and
JamesKovacs
|
|
||
| // Sets the connection URI than includes the replica set name | ||
| const string connectionUri = "mongodb://host1:27017,host2:27017,host3:27017"; |
There was a problem hiding this comment.
I think you forgot to include the replica set name here?
There was a problem hiding this comment.
I believe the comment here is incorrect! Can fix it.
There was a problem hiding this comment.
@sanych-sun Another question... If we don't specify the replica set name here, wouldn't it be considered a standalone cluster?
There was a problem hiding this comment.
If we do not specify the replicaset name, it should be automatically discovered. However it's recommended to include the replicaset into the connection string if possible, to avoid wrong initialization in some corner cases (for example if connection seed list contains several hosts which are connected to a different replicasets - then result of connecting might depends on the fact what server reply first.)
Pull Request Info
PR Reviewing Guidelines
JIRA - https://jira.mongodb.org/browse/DOCSP-49054
Staging Links
Self-Review Checklist