-
Type: Bug
-
Resolution: Done
-
Priority: Minor - P4
-
None
-
Affects Version/s: 2.2.2
-
Component/s: Diagnostics
-
None
-
ALL
In this case, a db.currentOp(true) was issued on a mongos shell. Presumably, this will collect all db.currentOp(true) outputs from the shards, combine them and return the end result.
I'm not sure if there is an easy way to avoid the problem. Perhaps it should only return what can fit in the 16MB document, rather than returning the error message. Or fail gracefully with a better error message.
mongos> db.currentOp(true) Mon Jan 21 19:35:38 uncaught exception: error { "$err" : "Invalid BSONObj size: 17828054 (0xD6081001) first element: 0: { opid: "xxx:xxxxxxx", active: false, op: "update", ns: "xxxx.xxxx", query: { _id: "xxxxxx" }, client_s: "xxxxxxxxx:xxxxx", desc: "xxxxxxxx", threadId: "xxxxxxxxxxxx", connectionId: xxxxxx, waitingForLock: false, numYields: 0, lockStats: { timeLockedMicros: { r: 0, w: 709 }, timeAcquiringMicros: { r: 0, w: 7 } } }", "code" : 10334 }
- depends on
-
SERVER-19318 currentOp command should return cursor
- Closed
-
SERVER-8261 system for commands to return cursors
- Closed