-
Type: Bug
-
Resolution: Duplicate
-
Priority: Critical - P2
-
None
-
Affects Version/s: 2.6.4
-
Component/s: Aggregation Framework, Security, Stability
-
None
-
Query
-
Fully Compatible
-
ALL
-
Not sure if this is the cause but I can easily reproduce an error that ultimate terminates the mongos process.
The Log is below, not sure if it helps as it doesn't appear to dump much information.
2014-09-29T11:33:15.759-0400 [initandlisten] connection accepted from 172.16.56.76:56969 #9845 (10 connections now open) 2014-09-29T11:33:24.262-0400 [conn9840] command Risk.$cmd command: aggregate { $msg: "query not recording (too large)" } keyUpdates:0 numYields:7 locks(micros) r:261753 reslen:29159 1083ms 2014-09-29T11:33:33.184-0400 [conn9841] command Risk.$cmd command: aggregate { $msg: "query not recording (too large)" } keyUpdates:0 numYields:7 locks(micros) r:261737 reslen:29159 1088ms 2014-09-29T11:33:36.965-0400 [conn9844] end connection 172.16.56.77:60524 (9 connections now open) 2014-09-29T11:33:36.965-0400 [initandlisten] connection accepted from 172.16.56.77:60526 #9846 (10 connections now open) 2014-09-29T11:33:45.954-0400 [conn9845] end connection 172.16.56.76:56969 (9 connections now open) 2014-09-29T11:33:45.954-0400 [initandlisten] connection accepted from 172.16.56.76:56974 #9847 (10 connections now open) 2014-09-29T11:33:46.065-0400 [conn9840] *** unhandled exception 0xC00000FD at 0x00007FF9D70DB2D4, terminating 2014-09-29T11:33:46.065-0400 [conn9840] *** stack trace for unhandled exception:
- is related to
-
SERVER-8433 Aggregating deeply-nested documents can cause stack overflow
- Closed
-
SERVER-13661 Increase the maximum allowed depth of query objects
- Closed