Known Issues
5279 tracked MongoDB server issues from Jira with status, affected versions, and resolution details.
SERVER-138509ClosedFixed
Add metric checks to checkpoint_validation_standby_restart.js
Fixed Versions
9.1.0-rc09.1.0-rc1025
SERVER-138606ClosedFixed
Disable validation on the truncateRange user collection in magic_restore_oplog_application.js
magic_restore_oplog_application.js uses truncateRange on a clustered collection with no secondary indexes:
Collection validation at the end of the test occasionally fails after SERVER-138410 because the size/count change from the truncate operation is not accounted for. See patch [1|https://spruce.corp.mongodb.com/task/mongodb_mongo_master_enterprise_amazon_linux2023_arm64_disagg_no_feature_flags_extra_system_deps_display_disagg_storage_patch_851eb168ff8127e309619c1138a1cf2e0fd1f7aa_6aea3d20f
Fixed Versions
9.1.0-rc09.1.0-rc1025
GODRIVER-4227ClosedDone
mongo-go-driver - PR #2700: Bump testdata/specifications from `f5ba7f7` to `775c4bc`
[dependabot[bot]|https://github.com/apps/dependabot] has created [PR #2700: Bump testdata/specifications from `f5ba7f7` to `775c4bc`|https://github.com/mongodb/mongo-go-driver/pull/2700] in [mongo-go-driver|https://github.com/mongodb/mongo-go-driver]
NODE-5150Backlog
client metadata appName truncation breaks when unicode characters straddle the 128th byte
makeClientMetadata truncates the appname using Buffer.subarray() and buffer.toString('utf8'):
This breaks when encoding a string that has a multi-byte unicode character that straddles the 128th byte in the array because `toString('utf8')' replaces the invalid bytes with the unicode replacement character:
h4. Acceptance Criteria
Fix our string length truncation so that we never produce a string that's > 128 bytes.
Components
Connection Layer
SERVER-135207ClosedFixed
Allow setting CS server parameters at startup if possible
Some of our server parameters can only be set at runtime. For example, [reshardingCollectionClonerWriteThreadCount|https://github.com/10gen/mongo/blob/fb18782b9af47f7b8d96ee1224e5c0b38e24d7fe/src/mongo/db/s/resharding/resharding_server_parameters.idl#L78-L88]. Certainly in this case, there is no reason that this cannot be set at startup, but also in general it's unclear if it ever makes sense for a parameter to be only runtime settable.
Furthermore, non-startup settable parameters complicate
Fixed Versions
9.1.0-rc09.1.0-rc1025
SERVER-138626ClosedFixed
Fix flakey join plan cache golden test
This patch adds a call to fsync before running the plan cache test to ensure that on disk stats are properly initialized at the first storage engine checkpoint. Prior to this change, the join plan cache invalidation golden test was flakey with a fail rate of 1-5% due to the race between first checkpoint and query.
Fixed Versions
9.1.0-rc09.1.0-rc1025
SERVER-104265ClosedFixed
Disable feature flag gFeatureFlagReshardingCloneNoRefresh
In light of findings reported in SERVER-104258 where resharding can hang when gFeatureFlagReshardingCloneNoRefresh is true, we will disable the feature until we have a proper fix and enable it again with the fix.
Fixed Versions
8.2.0-rc08.1.1
SERVER-104258ClosedFixed
Resharding Can Hang If Recipient Fails During ShardsvrReshardRecipientClone
If the [featureFlagReshardingCloneNoRefresh is enabled|https://github.com/10gen/mongo/blob/9ba3c40f75957b189ab599eaa8afea2fbe873810/src/mongo/db/s/resharding/resharding_coordinator.inl#L348-L350], the coordinator will use [ShardsvrReshardRecipientClone|https://github.com/10gen/mongo/blob/9ba3c40f75957b189ab599eaa8afea2fbe873810/src/mongo/db/s/resharding/resharding_coordinator.inl#L1646-L1659] to tell the recipients to begin cloning.
When the coordinator sends this command, it will block until
Affected Versions
8.1.0-rc4
Fixed Versions
8.3.0-rc0
SERVER-107955ClosedFixed
ReshardingOplogFetcher Will Not Be Restarted If Failing Over While Building Indexes
The resharding oplog fetchers are [started|https://github.com/10gen/mongo/blob/74e1f27e6aaa6d399b790e28b95db97043355be8/src/mongo/db/s/resharding/resharding_recipient_service.cpp#L988] in [_ensureDataReplicationStarted|https://github.com/10gen/mongo/blob/74e1f27e6aaa6d399b790e28b95db97043355be8/src/mongo/db/s/resharding/resharding_recipient_service.cpp#L980], which is called only in the [cloning|https://github.com/10gen/mongo/blob/74e1f27e6aaa6d399b790e28b95db97043355be8/src/mongo/db/s/reshardin
Fixed Versions
8.3.0-rc0
SERVER-138459ClosedFixed
Plan StreamingGroupNode for compound group keys
Extend the planner's streaming {{$group}} choice from SERVER-136171 to object {{_id}} keys whose members are all plain field paths, such as {{_id: {x: "$a", y: "$b"}}}.
* Every member must be known not to be an array ({{nonArrayIdFields}}).
* The distinct source paths must be exactly the first fields of the access plan's base sort pattern, in any order and any directions.
* Nested objects, computed members, and equality-bound key fields still fall back to hash {{$group}}.
Fixed Versions
9.1.0-rc09.1.0-rc1025
SERVER-136171ClosedFixed
Make StreamingGroupNode in extendWithAggPipeline when possible
Fixed Versions
9.1.0-rc09.1.0-rc1025
SERVER-138643ClosedDuplicate
Remove resharding op cap dependency on thread pool max counts and reset thread pool to original defaults
After SERVER-138049 lands, the maximum number of resharding operations that can run concurrently will no longer depend on/be a function of the server parameters for maximum thread pool count for coordinator/donors/recipients. We should change the logic so that it no longer depends on those values, and we should also reset those values back to their defaults (coordinator = 5, donor = 2, recipient = 8).
The cap can be some hard coded value for now. Afterwards, SERVER-138298 can make it a cluste
GODRIVER-3504ClosedWon't Do
Newlines in AWS web identity token file break AWS auth
h3. Detailed steps to reproduce the problem?
Reported in https://github.com/mongodb/mongo-go-driver/pull/1965
Some cloud platforms include a newlines in AWS web token files (i.e. using {{AssumeRoleWithWebIdentity}}). Currently, the Go Driver doesn't query-encode the values when building the URL to call AWS STS (see [here|https://github.com/mongodb/mongo-go-driver/blob/e3670f707772984c5aac0002c272d466ba114ea8/internal/credproviders/assume_role_provider.go#L92]), so parsing the URL fails with
SERVER-138635ClosedFixed
Exclude persistent_stats_upgrade_downgrade from multiversion_auth
Tag persistent_stats_upgrade_downgrade.js auth_incompatible: with auth, mongos hides system.* collections from getCollectionNames(). Fixes BFG-3776316.
Fixed Versions
9.1.0-rc09.1.0-rc1025
GODRIVER-4228ClosedDuplicate
mongo-go-driver - PR #2680: enforce ALLOWED_HOSTS before sending a cached OIDC access token
Tracks: https://github.com/mongodb/mongo-go-driver/pull/2680
SERVER-70200ClosedFixed
Implement UUID::Hash using bytes from UUID instead of murmur3
Since UUIDs are themselves randomly generated, one alternative to generating a hash for an UUID with a traditional hash algorithm is to take 4 bytes from the UUID itself and use that as the Hash. Care would be taken to avoid copying over the portions of the UUID that are deterministically set.
Fixed Versions
7.2.0-rc0
SERVER-138601In Code Review
BSONObj checks use bson_details tassert helper
Fixed Versions
9.1.0-rc09.1.0-rc1025
SERVER-83487ClosedFixed
Make UserRequest an interface
We should convert the UserRequest object to an interface and have specific types for X509 and OIDC, and a separate general userRequest for most other request types.
For X509 and OIDC, there should be a space to store the X509 certificate / name etc and the JWT respectively.
Fixed Versions
8.1.0-rc0
SERVER-137863ClosedDuplicate
Prevent analyze on local collection
Local collections are not subject to replication and are only used internally (customers cannot create them). Prevent persisting stats for them.