-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Labels:None
-
Cluster Scalability
-
Cluster Scalability 2024-5-13
SERVER-89182 adds a concurrency suite with random migrations and config shard transitions, and can hit a CollectionUUIDMismatch error in config.system.sessions in the background metadata consistency checker in jstests/concurrency/fsm_workloads/add_remove_shards_killop.js
This ticket tracks diagnosing that failure and either fixing it or officially disabling it in the config shard transition suite.
Example failure:
2024-04-23T14:42:38.717Z assert: [0] != [2] are not equal : Found metadata inconsistencies: [
{
"type" : "CollectionUUIDMismatch",
"description" : "Found collection on non primary shard with mismatching UUID",
"details" : {
"namespace" : "config.system.sessions",
"shard" : "shard-rs2",
"localUUID" : UUID("1c302649-cfad-4b0d-8469-c592c1595b29"),
"uuid" : UUID("31cf2c8b-78f7-4d43-94c3-81cde6b87657")
}
},
{
"type" : "CollectionOptionsMismatch",
"description" : "Found collection with mismatching options across shards and/or config server",
"details" : {
"namespace" : "config.system.sessions",
"options" : [
{
"shards" : [
"shard-rs2"
],
"options" : {
"uuid" : UUID("1c302649-cfad-4b0d-8469-c592c1595b29")
}
},
{
"shards" : [
"config"
],
"options" : {
"uuid" : UUID("31cf2c8b-78f7-4d43-94c3-81cde6b87657")
}
}
]
}
}
]
doassert@src/mongo/shell/assert.js:20:14
assert.eq@src/mongo/shell/assert.js:176:17
checkMetadataConsistency@/data/mci/14f96bb8a1a9f0e6768827131fd83bfe/src/jstests/libs/check_metadata_consistency_helpers.js:53:20
run@/data/mci/14f96bb8a1a9f0e6768827131fd83bfe/src/jstests/libs/check_metadata_consistency_helpers.js:61:13
@jstests/hooks/run_check_metadata_consistency.js:33:28
- depends on
-
SERVER-89971 ChunkMigrationInserters shouldn't be allowed to implicitly create the collection for the chunk being migrated
-
- Open
-