DBCommandCursor will route getMore and killCursor operations to the current primary of the replica set. Since a cursor that exists on the primary remains following a stepdown, the DBCommandCursor will route a getMore or killCursor operation to the wrong node. A similiar situation can arise if slaveOk is set on the replica-set connection.
- is related to
-
SERVER-20708 getMore and killCursors commands should ignore the value of the slaveOk bit received from the client
- Closed
-
SERVER-22347 Mongo shell replica set connections must use legacy readMode
- Closed
-
SERVER-23280 Add variant of jsCore_small_oplog_rs passthrough task which starts shell with replica set connection string
- Closed
- related to
-
SERVER-29641 checkReplicatedDataHashes() throws a TypeError when replSetTest uses mongobridge
- Closed
-
SERVER-33284 Garbage collection of DBCommandCursor created via replica set connection may fail to run killCursors command
- Closed
-
SERVER-20770 Consolidate the two code paths for running find commands in the mongo shell
- Backlog