-
Type: Bug
-
Resolution: Done
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Admin, Diagnostics, Logging
-
None
-
Fully Compatible
-
ALL
-
Query 2017-04-17, Query 2017-05-08, Query 2017-05-29, Query 2017-06-19, Query 2017-07-10
-
0
mongos> db.currentOp(true) 2015-07-07T11:26:00.759-0700 error: { "$err" : "BufBuilder attempted to grow() to 134217728 bytes, past the 64MB limit.", "code" : 13548 } at src/mongo/shell/query.js:131
There are 225 connections to the mongos, with 40 shards, each
with a 5-member replica set. lsof shows ~4600 open connections to the mongos process.
Trying to grow a buffer to 134 MB for the output of 4600 connections seems a little large (~32 kB/connection entry), but making the command scale is the goal.
Introducing a cursor to the command (and others like it) would allow it to work on arbitrarily sized clusters.
- is depended on by
-
SERVER-8259 if db.currentOp(true) exceeds 16MB, it returns invalid BSON size errors
- Closed
- is duplicated by
-
SERVER-8136 allow db.currentOp() from mongos to show the query jobs performed on secondaries
- Closed
- is related to
-
SERVER-23260 Report original query with getMore in log, profiler and currentOp
- Closed
-
SERVER-23267 Add test coverage for inclusion of namespace, command object and planSummary in currentOp
- Closed
- related to
-
SERVER-19317 Run all tests against large sharded clusters
- Closed
-
SERVER-29546 Add hostname to standard $currentOp output, and include shard name when run on a cluster
- Closed