Using ReadPreference.Secondary causes issues if read_secondary is not supplied with true #741
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.
Allowed for leaving read_secondary option off of ReplicaSet constructor as we have enough information from the new ReadPreference object to know the secondary allowed setting.
Supplying ReadPreference.SecondaryWhatever without read_secondary=true causes allRawConnections() to return with no secondaries in the connections list (to db.authenticate()) and ultimately cause unauthenticated servers to be in the replicaset connection pool but still used and ultimately downstream auth failures.