This repository has been archived by the owner on Oct 2, 2023. It is now read-only.
add read preference to mongo config #357
Open
Conversation
This file contains 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
add read preference to mongo config
rvema
suggested changes
Oct 13, 2021
trafico-bot
bot
added
⚠️ Changes requested
add read proference property to configuration mongo cli
trafico-bot
bot
added
🔍 Ready for Review
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Read preference describes how MongoDB clients route read operations to the members of a replica set.
SecondaryPreferred is operations read from secondary members but if no secondary members are available, operations read from the primary
This greatly optimizes the load on the database. the writing operations are carried out on the primary node and the reading operations on the secondary ones. It makes better use of secondary resources, it also increases the speed of operations since the primary node is not overloaded. In case you do not have a replica set, the operations are performed in the primary node without problems.