When executing the plan below, we hit this invariant. The bug seems to involve a combination of fetching, shard filtering and orphans.
{ "isCached" : false, "stage" : "SORT_KEY_GENERATOR", "inputStage" : { "stage" : "DISTINCT_SCAN", "keyPattern" : { "shardKey" : 1, "notShardKey" : 1 }, "indexName" : "shardKey_1_notShardKey_1", "isMultiKey" : false, "multiKeyPaths" : { "shardKey" : [ ], "notShardKey" : [ ] }, "isUnique" : false, "isSparse" : false, "isPartial" : false, "isShardFiltering" : true, "isFetching" : true, "indexVersion" : 2, "direction" : "forward", "indexBounds" : { "shardKey" : [ "(\"chunk1_s0\", {})" ], "notShardKey" : [ "[MinKey, MaxKey]" ] } } }
- is depended on by
-
SERVER-95934 Allow distinct_scan_shard_filtering.js to run on TSAN variants
- Closed
- related to
-
SERVER-93389 WiredTigerSessionCache does not properly dispose of sessions released after rollback
- Closed