Fixing recommendations #1582
Closed
Fixing recommendations #1582
Conversation
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
nearest uses closest by ping time which is not what fastest implies. The recommendation on increasing throughput is highly misleading - there is no way that someone can expect reduced disk I/O and increased throughput by reading from nearest secondary unless their specific problem was something extremely specific (and uncommon!)
|
IMO we should accept this patch, and also note in the "primary" mode graf that it's the default. I can work on a replacement for the graf Asya is deleting; the replacement will emphasize the specialized purpose of "nearest" with a very high secondaryAcceptableLatencyMS. |
|
do you want a docs ticket to track your work on that paragraph. |
|
merged and back/forward ported. see https://jira.mongodb.org/browse/DOCS-2717 for future work. |
mongo-cr-bot
pushed a commit
that referenced
this pull request
Aug 4, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
nearest uses closest by ping time which is not what fastest implies.
The recommendation on increasing throughput is highly misleading - there is no way that someone can expect reduced disk I/O and increased throughput by reading from nearest secondary unless their specific problem was something extremely specific (and uncommon!)