-
Type:
Task
-
Resolution: Done
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Catalog and Routing
-
CAR Team 2024-05-27, Cluster Scalability 2024-5-13
-
None
-
3
-
None
-
None
-
None
-
None
-
None
-
None
SERVER-89182 adds a concurrency suite with random migrations and config shard transitions, and time series tests with collMod can fail the background metadata consistency checker because of mismatched collection options across shards.
This ticket tracks diagnosing this failure and either fixing it or officially disabling the affected tests in the config shard transition suite.
The disabled tests:
- jstests/concurrency/fsm_workloads/timeseries_collmod_granularity_update.js
- jstests/concurrency/fsm_workloads/timeseries_agg_out.js
Example failure:
uncaught exception: Error: [0] != [1] are not equal : F
{
"type" : "CollectionOptionsMismatch",
"description" : "Found collection with mismatching
"details" : {
"namespace" : "test33_fsmdb0.system.buckets.shard
"options" : [
{
"options" : {
"timeseriesFields" : {
"timeField" : "time",
"metaField" : "meta",
"bucketRoundingSeconds" : 2,
"bucketMaxSpanSeconds" : 2
}
},
"shards" : [
"shard-rs1"
]
},
{
"options" : {
"timeseriesFields" : {
"timeField" : "time",
"metaField" : "meta",
"bucketRoundingSeconds" : 3,
"bucketMaxSpanSeconds" : 3
}
},
"shards" : [
"config"
]
}
]
}
}
] :
doassert@src/mongo/shell/assert.js:20:14
assert.eq@src/mongo/shell/assert.js:176:17
checkMetadataConsistency@/data/mci/30cd7c5be4bc1185d289
run@/data/mci/30cd7c5be4bc1185d289423e4f37697e/src/jste
@jstests/hooks/run_check_metadata_consistency.js:33:28
- depends on
-
SERVER-90117 Interrupting collMod can leave behind inconsistent collection options
-
- Closed
-