ISSUE SUMMARY
In the mongo shell, the killOp, currentOp, and fsyncUnlock operations produce errors with non-primary read preferences.
USER IMPACT
In the mongo the killOp, currentOp, and fsyncUnlock operations fail when sent with non-primary read preferences and the client disconnects. Drivers are not affected by this issue as they currently remove read preference before sending these commands.
WORKAROUNDS
Set primary read preference while running the killOp, currentOp, and fsyncUnlock operations in the shell.
AFFECTED VERSIONS
MongoDB 2.4.0 to 3.0.2
FIX VERSION
The fix is included in the 3.0.3 production release.
Original description
When I set a read preference, e.g. db.getMongo().setReadPref("primary") or db.getMongo().setReadPref("secondary"), db.currentOp() fails both on mongod and mongos.
- is related to
-
SERVER-7775 Make special commands (inprog, killop, unlock) go through the standard command codepath
-
- Closed
-
- related to
-
SERVER-24341 Find on admin.$cmd.sys.inprog asserts on top-level $query field
-
- Closed
-