Info

When running an aggregation with $group and $first and $last for "$$ROOT" I get this error: 2019-09-04T13:46:11.118-0400 E QUERY [js] Error: command failed: { "operationTime" : Timestamp(1567619155, 1218), "ok" : 0, "errmsg" : "assertion src/mongo/db/pipeline/value.cpp:1368", "code" : 8, "codeName" : "UnknownError", "$clusterTime" : { "clusterTime" : Timestamp(1567619155, 1218), "signature" : { "hash" : BinData(0,"Ra+UKIAYLDFuDOJc2Q6v16BRwsI="), "keyId" : NumberLong("6694721349983666177") } } } : aggregate failed : _getErrorWithCode@src/mongo/shell/utils.js:25:13 doassert@src/mongo/shell/assert.js:18:14 _assertCommandWorked@src/mongo/shell/assert.js:536:17 assert.commandWorked@src/mongo/shell/assert.js:620:16 DB.prototype._runAggregate@src/mongo/shell/db.js:260:9 DBCollection.prototype.aggregate@src/mongo/shell/collection.js:1062:12 @(shell):1:1

Top User Comments

asya commented on Thu, 30 Apr 2020 15:06:02 +0000: Root cause of this was in some cases spilling to disk and having the file on disk grow to some size larger than 4GBs. xgen-internal-githook commented on Tue, 29 Oct 2019 13:37:24 +0000: Author: {'username': 'gormanb', 'email': 'bernard.gorman@mongodb.com', 'name': 'Bernard Gorman'} Message: SERVER-43151 DSGroup should record current spill file offset as std::streampos (cherry picked from commit e20b65008f4738d73d338ed1af464ec8a1749742) Branch: v4.2 https://github.com/mongodb/mongo/commit/c49dfbfae5589f189ec4b8b8469cf9b255036671 xgen-internal-githook commented on Tue, 29 Oct 2019 13:24:15 +0000: Author: {'username': 'gormanb', 'email': 'bernard.gorman@mongodb.com', 'name': 'Bernard Gorman'} Message: SERVER-43151 DSGroup should record current spill file offset as std::streampos (cherry picked from commit e20b65008f4738d73d338ed1af464ec8a1749742) Branch: v4.0 https://github.com/mongodb/mongo/commit/198cdb8c0774682e947cdf46caa6ea13bde77b01 xgen-internal-githook commented on Tue, 29 Oct 2019 13:16:07 +0000: Author: {'username': 'gormanb', 'email': 'bernard.gorman@mongodb.com', 'name': 'Bernard Gorman'} Message: SERVER-43151 DSGroup should record current spill file offset as std::streampos (cherry picked from commit e20b65008f4738d73d338ed1af464ec8a1749742) Branch: v3.4 https://github.com/mongodb/mongo/commit/ec4db6d457448130a55ad41d4d42c1449bbeadf1 xgen-internal-githook commented on Tue, 29 Oct 2019 13:11:03 +0000: Author: {'name': 'Bernard Gorman', 'username': 'gormanb', 'email': 'bernard.gorman@mongodb.com'} Message: SERVER-43151 DSGroup should record current spill file offset as std::streampos (cherry picked from commit e20b65008f4738d73d338ed1af464ec8a1749742) Branch: v3.6 https://github.com/mongodb/mongo/commit/db36f1024d6623a2bce4570118c1ea4b9968f7dc xgen-internal-githook commented on Mon, 28 Oct 2019 21:56:58 +0000: Author: {'name': 'Bernard Gorman', 'username': 'gormanb', 'email': 'bernard.gorman@mongodb.com'} Message: SERVER-43151 DSGroup should record current spill file offset as std::streampos Branch: master https://github.com/mongodb/mongo/commit/e20b65008f4738d73d338ed1af464ec8a1749742 milkie commented on Fri, 18 Oct 2019 13:09:58 +0000: The symptoms described in this ticket does not suggest data corruption on disk, but does suggest BSON corruption in memory with the use of $$ROOT. brian.lane commented on Fri, 18 Oct 2019 05:04:42 +0000: Hey vikas.ramnani and eric.sedor - Since its happening in both 4.0 and 4.2, I don't think this is related to the different versions of snappy. I am going to pass this over to execution, who can direct it to another team as needed. -Brian

Steps to Reproduce