Details
-
Task
-
Status: Closed
-
Major - P3
-
Resolution: Fixed
-
None
-
Fully Compatible
-
Sharding EMEA 2022-11-28, Sharding EMEA 2022-12-12, Sharding EMEA 2022-12-26, Sharding EMEA 2023-01-09, Sharding EMEA 2023-01-23, Sharding EMEA 2023-02-06, Sharding EMEA 2023-02-20
Description
These lines can be removed from jstests/libs/check_orphans_are_deleted_helpers.js after the changes from SERVER-6491. Removing this escape hatch will increase our confidence the sharding consistency checks are truly running and not being inadvertently skipped.
// It is possible for a test to drop the shard key index. We skip running the check for
|
// orphan documents being deleted from that collection if it doesn't have a shard key
|
// index.
|
const hintRes = shardConn.getDB(dbName).runCommand({
|
find: collName,
|
hint: collDoc.key,
|
limit: 1,
|
singleBatch: true, |
});
|
|
if (hintRes.ok !== 1) { |
assert(
|
/hint provided does not correspond to an existing index/.test(hintRes.errmsg),
|
() => {
|
return 'expected query failure due to bad hint: ' + tojson(hintRes); |
});
|
print('Failed to find shard key index on ' + ns + |
' so skipping check for orphan documents being deleted'); |
return; |
}
|
Attachments
Issue Links
- is related to
-
SERVER-46059 Add hook at the end of concurrency tests to assert that orphans are eventually cleaned up
-
- Closed
-
-
SERVER-69491 Run CheckRoutingTableConsistency hook as part of jstestfuzz_sharded*.yml test suites
-
- Closed
-
-
SERVER-6491 Prevent dropping shard key index when alternative index doesn't exist
-
- Closed
-
- related to
-
SERVER-46068 Add hook at the end of sharding passthrough tests that do migrations to check that orphans are eventually cleaned up
-
- Backlog
-