Info
While we were running some aggregation queries the mongod process stopped/crashed all of a sudden. These is the extract from the connection that generated this , may be all the queries were not logged
2017-07-25T12:43:43.395-0400 I COMMAND [conn2108957] command esp-9.fitch_entity command: aggregate { aggregate: "fitch_entity", pipeline: [ { $match: { transactionList: { $exists: true } } }, { $unwind: "$transactionList" }, { $match: { transactionList.transactionID: 96247516.0 } }, { $lookup: { from: "fitch_ratable", localField: "groupID", foreignField: "groupID", as: "bonds" } }, { $unwind: "$bonds" }, { $project: { bonds: 1.0 } } ], cursor: { batchSize: 50 }, allowDiskUse: false } cursorid:247538249648 keyUpdates:0 writeConflicts:0 numYields:1216 reslen:196102 locks:{ Global: { acquireCount: { r: 2484 } }, Database: { acquireCount: { r: 1242 } }, Collection: { acquireCount: { r: 1242 } } } protocol:op_query 2728ms
2017-07-25T12:44:52.085-0400 F -
[conn2108957] Invalid access at address: 0x20
2017-07-25T12:44:52.133-0400 F -
[conn2108957] Got signal: 11 (Segmentation fault).
Top User Comments
thomas.schubert commented on Mon, 28 Aug 2017 18:31:00 +0000:
Hi amol.gholap@fitchratings.com,
We haven’t heard back from you for some time, so I’m going to mark this ticket as resolved. If this is still an issue for you, please provide additional information and we will reopen the ticket.
Regards,
Thomas
thomas.schubert commented on Tue, 25 Jul 2017 20:20:01 +0000:
Hi amol.gholap@fitchratings.com,
Would you please provide the complete log file from the affected mongod?
Thank you,
Thomas
