DOCSP-51321: Configure CRUD operations#113
Merged
norareidy merged 3 commits intomongodb:comp-covfrom Jul 21, 2025
Merged
Conversation
✅ Deploy Preview for docs-kotlin-sync ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
🔄 Deploy Preview for docs-kotlin-sync processing
|
mongoKart
approved these changes
Jul 9, 2025
Collaborator
mongoKart
left a comment
mongoKart
left a comment
There was a problem hiding this comment.
LGTM w/ some small suggestions
Comment on lines
+73
to
+79
| - ``secondary`` read preference: Read operations retrieve data from | ||
| secondary replica set members. | ||
| - ``LOCAL`` read concern: Read operations return the instance's most recent data | ||
| without guaranteeing that the data has been written to a majority of the replica | ||
| set members. | ||
| - ``W2`` write concern: The primary replica set member and one secondary member | ||
| must acknowledge the write operation. |
Collaborator
There was a problem hiding this comment.
No periods needed
Suggested change
| - ``secondary`` read preference: Read operations retrieve data from | |
| secondary replica set members. | |
| - ``LOCAL`` read concern: Read operations return the instance's most recent data | |
| without guaranteeing that the data has been written to a majority of the replica | |
| set members. | |
| - ``W2`` write concern: The primary replica set member and one secondary member | |
| must acknowledge the write operation. | |
| - ``secondary`` read preference: Read operations retrieve data from | |
| secondary replica set members | |
| - ``LOCAL`` read concern: Read operations return the instance's most recent data | |
| without guaranteeing that the data has been written to a majority of the replica | |
| set members | |
| - ``W2`` write concern: The primary replica set member and one secondary member | |
| must acknowledge the write operation |
Collaborator
Author
There was a problem hiding this comment.
I think since these are full sentences, they should have periods - https://www.mongodb.com/docs/meta/style-guide/style/lists/#list-items
Comment on lines
+115
to
+120
| - ``primary`` read preference: Read operations retrieve data from | ||
| the primary replica set member. | ||
| - ``MAJORITY`` read concern: Read operations return the instance's most recent data | ||
| that has been written to a majority of replica set members. | ||
| - ``W1`` write concern: The primary replica set member must acknowledge the | ||
| write operation. |
Collaborator
There was a problem hiding this comment.
No periods needed
Suggested change
| - ``primary`` read preference: Read operations retrieve data from | |
| the primary replica set member. | |
| - ``MAJORITY`` read concern: Read operations return the instance's most recent data | |
| that has been written to a majority of replica set members. | |
| - ``W1`` write concern: The primary replica set member must acknowledge the | |
| write operation. | |
| - ``primary`` read preference: Read operations retrieve data from | |
| the primary replica set member | |
| - ``MAJORITY`` read concern: Read operations return the instance's most recent data | |
| that has been written to a majority of replica set members | |
| - ``W1`` write concern: The primary replica set member must acknowledge the | |
| write operation |
Comment on lines
+138
to
+144
| - ``primaryPreferred`` read preference: Read operations retrieve data from | ||
| the primary replica set member, or secondary members if the primary is unavailable. | ||
| - ``AVAILABLE`` read concern: Read operations return the instance's most recent data | ||
| without guaranteeing that the data has been written to a majority of the replica | ||
| set members. | ||
| - ``MAJORITY`` write concern: The majority of all replica set members | ||
| must acknowledge the write operation. |
Collaborator
There was a problem hiding this comment.
No periods needed
Suggested change
| - ``primaryPreferred`` read preference: Read operations retrieve data from | |
| the primary replica set member, or secondary members if the primary is unavailable. | |
| - ``AVAILABLE`` read concern: Read operations return the instance's most recent data | |
| without guaranteeing that the data has been written to a majority of the replica | |
| set members. | |
| - ``MAJORITY`` write concern: The majority of all replica set members | |
| must acknowledge the write operation. | |
| - ``primaryPreferred`` read preference: Read operations retrieve data from | |
| the primary replica set member, or secondary members if the primary is unavailable | |
| - ``AVAILABLE`` read concern: Read operations return the instance's most recent data | |
| without guaranteeing that the data has been written to a majority of the replica | |
| set members | |
| - ``MAJORITY`` write concern: The majority of all replica set members | |
| must acknowledge the write operation |
Comment on lines
+162
to
+169
| - ``secondaryPreferred`` read preference: Read operations retrieve data from | ||
| secondary replica set members, or the primary members if no secondary members are | ||
| available. | ||
| - ``AVAILABLE`` read concern: Read operations return the instance's most recent data | ||
| without guaranteeing that the data has been written to a majority of the replica | ||
| set members. | ||
| - ``UNACKNOWLEDGED`` write concern: Replica set members do not need to acknowledge | ||
| the write operation. |
Collaborator
There was a problem hiding this comment.
Suggested change
| - ``secondaryPreferred`` read preference: Read operations retrieve data from | |
| secondary replica set members, or the primary members if no secondary members are | |
| available. | |
| - ``AVAILABLE`` read concern: Read operations return the instance's most recent data | |
| without guaranteeing that the data has been written to a majority of the replica | |
| set members. | |
| - ``UNACKNOWLEDGED`` write concern: Replica set members do not need to acknowledge | |
| the write operation. | |
| - ``secondaryPreferred`` read preference: Read operations retrieve data from | |
| secondary replica set members, or the primary members if no secondary members are | |
| available | |
| - ``AVAILABLE`` read concern: Read operations return the instance's most recent data | |
| without guaranteeing that the data has been written to a majority of the replica | |
| set members | |
| - ``UNACKNOWLEDGED`` write concern: Replica set members do not need to acknowledge | |
| the write operation |
Comment on lines
+195
to
+199
| - **Shard**: A replica set that contains a subset of the sharded data. | ||
| - **Mongos**: A query router that provides an interface between your | ||
| application and the sharded cluster. | ||
| - **Config servers**: Servers that store the cluster's configuration settings | ||
| and metadata. |
Collaborator
There was a problem hiding this comment.
Suggested change
| - **Shard**: A replica set that contains a subset of the sharded data. | |
| - **Mongos**: A query router that provides an interface between your | |
| application and the sharded cluster. | |
| - **Config servers**: Servers that store the cluster's configuration settings | |
| and metadata. | |
| - **Shard**: A replica set that contains a subset of the sharded data | |
| - **Mongos**: A query router that provides an interface between your | |
| application and the sharded cluster | |
| - **Config servers**: Servers that store the cluster's configuration settings | |
| and metadata |
source/crud/configure.txt
Outdated
| distribute these requests across multiple servers, which avoids overwhelming | ||
| any one server and ensures optimal performance. | ||
|
|
||
| When connecting to a sharded cluster, the {+driver-short+} determines the closest mongos |
Collaborator
There was a problem hiding this comment.
Suggested change
| When connecting to a sharded cluster, the {+driver-short+} determines the closest mongos | |
| When connecting to a sharded cluster, the {+driver-short+} determines the closest ``mongos`` |
source/crud/configure.txt
Outdated
|
|
||
| When connecting to a sharded cluster, the {+driver-short+} determines the closest mongos | ||
| instance by calculating which one has the lowest network round-trip time. Then, the driver | ||
| determines the latency window by adding this mongos's average round-trip time to the |
Collaborator
There was a problem hiding this comment.
Suggested change
| determines the latency window by adding this mongos's average round-trip time to the | |
| determines the latency window by adding this ``mongos``'s average round-trip time to the |
source/crud/configure.txt
Outdated
| instance by calculating which one has the lowest network round-trip time. Then, the driver | ||
| determines the latency window by adding this mongos's average round-trip time to the | ||
| :ref:`localThresholdMS value <kotlin-sync-local-threshold>`. The driver load balances requests | ||
| across up to two random mongos instances that fall within the latency window. For each request, |
Collaborator
There was a problem hiding this comment.
Suggested change
| across up to two random mongos instances that fall within the latency window. For each request, | |
| across up to two random ``mongos`` instances that fall within the latency window. For each request, |
source/crud/configure.txt
Outdated
| latency window for server selection. This value determines the servers | ||
| that are eligible to receive read and write requests. | ||
|
|
||
| By default, the driver uses only mongos instances or replica set members whose |
Collaborator
There was a problem hiding this comment.
Suggested change
| By default, the driver uses only mongos instances or replica set members whose | |
| By default, the driver uses only ``mongos`` instances or replica set members whose |
source/crud/configure.txt
Outdated
|
|
||
| .. note:: | ||
|
|
||
| When selecting replica set members from a single mongos instance, the |
Collaborator
There was a problem hiding this comment.
Suggested change
| When selecting replica set members from a single mongos instance, the | |
| When selecting replica set members from a single ``mongos`` instance, the |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Pull Request Info
PR Reviewing Guidelines
Note to reviewers: this page is very similar to the corresponding Java Sync page, which was approved by writing & dbx: mongodb/docs-java#649
JIRA - https://jira.mongodb.org/browse/DOCSP-51321
Staging Links
Self-Review Checklist