Details
-
Bug
-
Status: Closed
-
Minor
-
Resolution: Fixed
-
1.9.3
-
None
Description
MissingLastRevSeekerTest actually does not run on MongoDB right now, but changing the test accordingly revealed an issue with the MongoDB specific implementation of MissingLastRevSeeker when running on a replica-set and secondary preferred read preference.
The class MongoMissingLastRevSeeker uses the configured read preference when checking for cluster node info entries that require recovery. This is inconsistent because the candidate nodes are read with primary read preference.
Attachments
Attachments
Issue Links
- relates to
-
OAK-6087 Avoid reads from MongoDB primary
- Closed