Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-15559

Fatal Exception: Deeply nested $cond drops mongod process

    • Query
    • Fully Compatible
    • ALL
    • Hide

      Startup: Default parameters (nothing special)
      Mongo Version: 2.6.4
      Driver: I'm using the official c# driver.
      Server: I have a 2 + 1 replica set and arbiter setup on 2 Win2012 R2 servers.
      Size: The collection is 18 million objects @ 17.1 GB.

      The query: A large aggregate query @ 76K on disk. The nature of the query is that I am sending up a very deeply nested $cond statement to offset mongos lack of a relation join construct.

      Show
      Startup: Default parameters (nothing special) Mongo Version: 2.6.4 Driver: I'm using the official c# driver. Server: I have a 2 + 1 replica set and arbiter setup on 2 Win2012 R2 servers. Size: The collection is 18 million objects @ 17.1 GB. The query: A large aggregate query @ 76K on disk. The nature of the query is that I am sending up a very deeply nested $cond statement to offset mongos lack of a relation join construct.

      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:
      

            Assignee:
            backlog-server-query Backlog - Query Team (Inactive)
            Reporter:
            mark.shaw@point72.com Mark Shaw
            Votes:
            0 Vote for this issue
            Watchers:
            11 Start watching this issue

              Created:
              Updated:
              Resolved: