Details
Description
Test kills all nodes in a config repl set except for one and tries to perform a read on it. However, it is possible that a background thread in mongos advances the latest config server opTime that the surviving secondary has yet to replicate and this will cause the read after opTime to timeout.
Attachments
Issue Links
- is related to
-
SERVER-27035 rs.compareOpTimes() throws exception when comparing with empty OpTime
-
- Closed
-