Known Issues
5166 tracked MongoDB server issues from Jira with status, affected versions, and resolution details.
GODRIVER-4258ClosedFixed
Consistent failure: TestFLE2CreateCollection panics on server 7.0.48 / 9.0.8+ and fails all 7.0+ integration tasks
h3. *Name of Failure:*
TestFLE2CreateCollection panics on server 7.0.48 / 9.0.8+ and fails all 7.0+ integration tasks
h3. *Link to task:*
https://spruce.corp.mongodb.com/version/6af3bc9a97d58300076ac0d3
7.0.45 and 9.0.4 accepted the deviating name, and 7.0.48 / 9.0.8 rejected it.
h3. *Context of when and why the failure occurred:*
The test creates a data collection named {{coll}} but passes an
{{escCollection}} name that belongs to a different collection:
internal/integration/clien
Fixed Versions
2.10.1
SERVER-139349In Progress
Enable stepdowns in disagg_concurrency_sharded_terminate_kill_primary_with_balancer
* Enable stepdowns in the suite (resolve this [TODO|https://github.com/10gen/mongo/blob/master/buildscripts/modules/atlas/matrix_suites/overrides/disagg.yml#L819-L820])
* Add "_stepdown" to the suite name
** disagg_concurrency_sharded_stepdown_terminate_kill_primary_with_balancer
Affected Versions
9.1.0-rc0
SERVER-139348Needs Scheduling
replSetGetStatus reports pingMs=0 for members that have a priorityPort configured
h3. Summary
When a replica set member has {{members[].priorityPort}} set (and {{disableReplicationUsageOfPriorityPort}} is false), {{replSetGetStatus}} always reports {{members[].pingMs: 0}} for that member. The heartbeat RTT is recorded, but under a different key than the one {{replSetGetStatus}} reads.
h3. Cause
* Heartbeats are sent to {{getHostAndPortPriority()}} ({{replication_coordinator_impl_heartbeat.cpp}}, {{auto target = rsc.getMemberAt(i).getHostAndPortPriority();}}). The ping stats
SERVER-138619In Code Review
Refactor to harden in-flight OpCtx logic
Coverity issue SERVER-138382, pointed to the logic around managing in-flight OpCtx values as a potential use-after-free case. The analysis turned out to be a false positive and I don't see any risks in the current logic, but the current implementation is fragile and future refactors could break the assumptions currently in place.
Here are a few possible strategies:
* CancelableOperationContext
** This is seemingly not viable, or any sort of cancellation-token-style approach, as a hard {{mar
NODE-7903Needs Review
Update dependencies for js-bson
h3. AC
* Merge dependabot PRs that are safe to merge (semver-compatible updates, including any standalone package-lock-only PRs)
* When updating the dev dependencies to latest available semver compatible versions ANY reformatting MUST be done in a separate pull request and should ONLY be done if the team agrees that it is an important improvement
* Check dev dependency major version updates
** Update the major version if and ONLY if this can be done with minimal code changes; otherwise, file
SERVER-135894Backlog
checkReferentialIntegrity(): single-session validation support for inserts
h2. Overview
Implement the core {{checkReferentialIntegrity\(\)}} mechanism that validates foreign keys on insert within a single session/transaction context, as prototyped in the POC. Includes detecting violations against the referenced \(parent\) collection.h1. Dev\-only: POC branch — [https://github.com/10gen/mongo/tree/mjrb/ri\-lockmgr2|https://github.com/10gen/mongo/tree/mjrb/ri-lockmgr2]
SERVER-121413ClosedFixed
Track the number of times the KEK has been used to encrypt DEKs
From a security perspective, we need to guarantee that a KEK has not been used 2^32-1 times to perform encryption. This follows a security guideline outlined by section 8.3 of [NIST GCM recommendations|section 8.3 of https://nvlpubs.nist.gov/nistpubs/Legacy/SP/nistspecialpublication800-38d.pdf].
This will likely have to be persisted in the keystore itself.
Fixed Versions
9.1.0-rc1026
SERVER-136296ClosedFixed
Enable standby collection validation fassert server parameter
Set the default value of {{fassertOnPerCollectionContinuousInternodeValidationFailure}} to {{{}true{}}}. When this parameter is set to true, fassert on a validation failure. Otherwise, log an error.
{color:#ff0000}This change enables checkpoint validation on all clusters, so checkpoint validation must be fully correct.{color}
Fixed Versions
9.1.0-rc09.1.0-rc1026
SERVER-136891Open
Update the OTEL prod allowlist with the combined step-up metric
SERVER-136676 combined the lower/upper bound metrics for failover unavailability, and added a label for planned/unplanned failover so we can differentiate them. Now that it's merged, we should update the [OTEL prod allowlist|https://github.com/10gen/mms/blob/5829760bdb34098dcd40afff36720802ae276c81/server/src/main/com/xgen/cloud/services/metrics/resource/usecase/privateConfig/prod/dedicated-mongo-otel-metrics.yaml#L29-L30] to use the [new combined step up metric|https://github.com/10gen/mongo/bl
SERVER-138704In Progress
Rework join node serialization in explain
In the explain {{queryPlan}} of join-optimized plans:
* Rename stages: {{NESTED_LOOP_JOIN_EMBEDDING}} to {{NESTED_LOOP_JOIN}}, {{HASH_JOIN_EMBEDDING}} to {{HASH_JOIN}}, {{INDEXED_NESTED_LOOP_JOIN_EMBEDDING}} to {{INDEXED_NESTED_LOOP_JOIN}}, {{INDEX_PROBE_NODE}} to {{INDEX_PROBE}}.
* Replace {{leftEmbeddingField}}/{{rightEmbeddingField}} on join nodes with {{embedAs}} on the root of each embedded collection's access path (no {{'none'}} sentinel).
* Serialize {{joinPredicates}} with output-documen
SERVER-134476Backlog
Address client CPU errors on resharding sys-perf workloads
From https://github.com/10gen/dsi/pull/5887.
After running patches to verify the changes in the above CR, I found that both the development branch and the master branch had various flaky test failures, including the following.
CPU Error
* reshard_collection_writes_to_other_coll_locust_test_execution
* reshard_collection_failover_test_execution
System Failed
* reshard_collection_burst_locust
* reshard_collection_2d2r_with_users_with_connection_storm_rate_limited_locust
Run a seri
SERVER-139076In Code Review
Report all estimated NDVs and rename selectivity in join explain ndvEstimates
In the detailed join explain output, change each {{ndvEstimates}} entry to:
* {{ndvs}} lists the NDV estimate of every side that was estimated: the smaller collection's side always, and the other side when it is available without sampling (unique index or persisted NDV statistics). It replaces {{assumedPkSide}}/{{ndv}}/{{ndvSource}}, which only show the larger of the two.
* Rename {{selectivity}} to {{joinPredicateSelectivity}} (= 1 / max(ndv)).
{{joinPredicateSel}} in {{cardinality_estimator.
SERVER-138703In Code Review
Rename detailed join estimate fields in explain
Rename {{cardinalityRHSBeforeJoinPred}} to {{innerCardinalityBeforeJoinEstimate}}, and in {{joinCostComponents}}: {{numDocsTransmitted}} to {{docsTransmitted}}, {{sequentialIOPages}} to {{sequentialIOs}}, {{randomIOPages}} to {{randomIOs}}. These fields stay behind {{internalEnableDetailedJoinExplain}}.
SERVER-136316Open
Remove member-array-order dependencies from replication in DSC
SERVER-134162 was caused by DSC replication code assuming that the members array in the replica set config is always listed in {{_id}} order. That assumption does not hold, as Atlas makes no guarantee about member order, and reconfigs routinely produce configs where members are out of {{_id}} order (for example, new electables inserted ahead of an existing read-only node: {{[_id: 1, _id: 0, _id: 2]}}). The skip-self check in heartbeating was the instance that surfaced in a HELP ticket, but the D
SERVER-134702ClosedFixed
Add connection pool metrics for connections created shortly after cancelation
To get a better idea of how often connection churn occurs, we should add a metric which tracks the number of connections that were created shortly after a connection in the same pool was closed due to cancelation. This will help us understand better the cost of canceling commands and may be used to help motivate something like inline cancelation.
Fixed Versions
9.1.0-rc09.1.0-rc1026
SERVER-138179Backlog
Write conflict can escape moveChunk command
It appears that the {{moveChunk}} command can return a write conflict error rather than retrying it internally.
SERVER-138728Backlog
Add a building-index phase to the resharding coordinator
Recipients build indexes after cloning, but the coordinator stays in the cloning phase for that entire duration. Donor history is currently unpinned when the coordinator advances to applying, even though the retained history is only needed until all recipients finish cloning.
Long-running index builds can extend the time donor history remains pinned, increasing cache pressure and adding system pressure.
The coordinator needs a distinct building-index phase that begins once every recipient
SERVER-139332ClosedFixed
Remove locals from structlog exception tracebacks
{{structlog}}'s default console renderer shows locals in exception tracebacks, which is noisy and can leak secrets.
This updates a logging utility to always configure logging without locals, by default.
Components
Testing Infrastructure
Fixed Versions
9.1.0-rc09.1.0-rc1026
SERVER-137524In Code Review
Define the PSAME feature flag
Add {{featureFlagPSAMEEnabled}} (default {{false}}) to gate the whole PSAME automation engine, independently of {{featureFlagPersistentStats}}.
See WRITING-11150, Upgrade/Downgrade Requirements and Behaviors.
SERVER-139335Open
test_api_version_compatibility should not break due to backports
This task is not compatible with the auto-reverter, because breaking changes can be merged to other branches and have a side effect of breaking master.
Possible solution:
Check the {{IGNORE_REMOVED_PARAMETERS_LIST}} or multiversion exclusion yml file on the prior branch before generating a task error.