An internal MongoDB Evergreen test is throwing an exception when it tries to interpret a record returned from WiredTiger but only to find it is empty.
assert: command failed: { "ok" : 0, "host" : "localhost:20000", "validateRes" : { "ok" : 0, "failed_res" : [ { "valid" : false, "warnings" : [ ], "errors" : [ "exception during collection validation: Overflow: Invalid advance (1) past end of buffer[0] at offset: 0" ], "extraIndexEntries" : [ ], "missingIndexEntries" : [ ], "advice" : "A corrupt namespace has been detected. See http://dochub.mongodb.org/core/data-recovery for recovery steps.", "ok" : 1, "$clusterTime" : { "clusterTime" : Timestamp(1591262189, 24), "signature" : { "hash" : BinData(0,"AAAAAAAAAAAAAAAAAAAAAAAAAAA="), "keyId" : NumberLong(0) } }, "operationTime" : Timestamp(1591262189, 24) } ] } } : Collection validation failed
We have seen the the same issue in the past, but had hoped that WT-6224 should fix it. However, the issue still reproduces after WT-6224 is merged.
- depends on
-
SERVER-53184 Abort in testing when validate fails to traverse an index entry
- Closed
- is related to
-
SERVER-51603 add log message for failing validation via exception path
- Closed
-
SERVER-51652 add better error handling for validate's use of KeyString
- Closed
-
WT-6542 Add an assert to ensure we are not unintentionally returning empty values
- Closed