-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
DB Integration & Observability
-
Fully Compatible
-
ALL
-
200
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Problem
filtering_sharded_cluster.js in the disagg_storage suite intermittently fails on the all-feature-flags TSAN variant with a schema mismatch in getDiagnosticData (also reachable via serverStatus) metrics:
"differences" : [
{
"path" : "serverStatus.metrics.disagg.pali.read.requestToPageReceivedLatencyMicros",
"error" : "Missing field in actual"
}
]
BF: https://jira.mongodb.org/browse/BF-47116
Failing test: src/mongo/db/modules/atlas/jstests/disagg_storage/metrics_filtering/filtering_sharded_cluster.js
Root cause
The fixture compares the metrics schema of an auth-enabled cluster against an auth-disabled cluster, which are two different mongod processes. disagg.pali.read.requestToPageReceivedLatencyMicros is a MovingAverageMetric (src/mongo/util/moving_average_metric.h). MovingAverageMetricPolicy::appendTo only publishes the field after at least one sample has been recorded, so the field is legitimately absent on a node that has not yet performed a page read. The schema comparison therefore reports it as a missing field.
Fix
Add the disagg.pali.read subsection to the non-determinism allowlist in src/mongo/db/modules/atlas/jstests/disagg_storage/libs/metrics_filtering/filtering_validation_opts.js (kServerStatusMetricsOpts.pathsToIgnoreContent). The getDiagnosticData options derive their paths from the serverStatus options by prefixing serverStatus., so the same entry covers both commands.
Acceptance Criteria
- filtering_sharded_cluster.js no longer fails when disagg.pali.read.requestToPageReceivedLatencyMicros is absent on one of the compared nodes.
- The change is limited to test validation options; no product behavior changes.