Releases: mongodb/node-mongodb-native
v6.8.2
6.8.2 (2024-09-12)
The MongoDB Node.js team is pleased to announce version 6.8.2 of the mongodb package!
Release Notes
Fixed mixed use of cursor.next() and cursor[Symbol.asyncIterator]
In 6.8.0, we inadvertently prevented the use of cursor.next() along with using for await syntax to iterate cursors. If your code made use of the following pattern and the call to cursor.next retrieved all your documents in the first batch, then the for-await loop would never be entered. This issue is now fixed.
const firstDoc = await cursor.next();
for await (const doc of cursor) {
// process doc
// ...
}Bug Fixes
Documentation
We invite you to try the mongodb library immediately, and report any issues to the NODE project.
v6.8.1
6.8.1 (2024-09-06)
The MongoDB Node.js team is pleased to announce version 6.8.1 of the mongodb package!
Release Notes
Fixed enableUtf8Validation option
Starting in v6.8.0 we inadvertently removed the ability to disable UTF-8 validation when deserializing BSON. Validation is normally a good thing, but it was always meant to be configurable and the recent Node.js runtime issues (v22.7.0) make this option indispensable for avoiding errors from mistakenly generated invalid UTF-8 bytes.
Bug Fixes
Documentation
We invite you to try the mongodb library immediately, and report any issues to the NODE project.
v6.8.0
6.8.0 (2024-06-27)
The MongoDB Node.js team is pleased to announce version 6.8.0 of the mongodb package!
Release Notes
Add ReadConcernMajorityNotAvailableYet to retryable errors
ReadConcernMajorityNotAvailableYet (error code 134) is now a retryable read error.
ClientEncryption.createDataKey() and other helpers now support named KMS providers
KMS providers can now be associated with a name and multiple keys can be provided per-KMS provider. The following example configures a ClientEncryption object with multiple AWS keys:
const clientEncryption = new ClientEncryption(keyVaultClient, {
'aws:key1': {
accessKeyId: ...,
secretAccessKey: ...
},
'aws:key2': {
accessKeyId: ...,
secretAccessKey: ...
},
clientEncryption.createDataKey('aws:key-1', { ... });Named KMS providers are supported for azure, AWS, KMIP, local and gcp KMS providers. Named KMS providers cannot be used if the application is using the automatic KMS provider refresh capability.
This feature requires mongodb-client-encryption>=6.0.1.
KMIP data keys now support a delegated option
When creating a KMIP data key, delegated can now be specified. If true, the KMIP provider will perform encryption / decryption of the data key locally, ensuring that the encryption key never leaves the KMIP server.
clientEncryption.createDataKey('kmip', { masterKey: { delegated: true } } );This feature requires mongodb-client-encryption>=6.0.1.
Cursor responses are now parsed lazily 🦥
MongoDB cursors (find, aggregate, etc.) operate on batches of documents equal to batchSize. Each time the driver runs out of documents for the current batch it gets more (getMore) and returns each document one at a time through APIs like cursor.next() or for await (const doc of cursor).
Prior to this change, the Node.js driver was designed in such a way that the entire BSON response was decoded after it was received. Parsing BSON, just like parsing JSON, is a synchronous blocking operation. This means that throughout a cursor's lifetime invocations of .next() that need to fetch a new batch hold up on parsing batchSize (default 1000) documents before returning to the user.
In an effort to provide more responsiveness, the driver now decodes BSON "on demand". By operating on the layers of data returned by the server, the driver now receives a batch, and only obtains metadata like size, and if there are more documents to iterate after this batch. After that, each document is parsed out of the BSON as the cursor is iterated.
A perfect example of where this comes in handy is our beloved mongosh! 💚
test> db.test.find()
[
{ _id: ObjectId('665f7fc5c9d5d52227434c65'), ... },
...
]
Type "it" for more
That Type "it" for more message would now print after parsing only the documents displayed rather than after the entire batch is parsed.
Add Signature to Github Releases
The Github release for the mongodb package now contains a detached signature file for the NPM package (named
mongodb-X.Y.Z.tgz.sig), on every major and patch release to 6.x and 5.x. To verify the signature, follow the instructions in the 'Release Integrity' section of the README.md file.
The LocalKMSProviderConfiguration's key property accepts Binary
A local KMS provider at runtime accepted a BSON Binary instance but the Typescript inaccurately only permitted Buffer and string.
Clarified cursor state properties
The cursor has a few properties that represent the current state from the perspective of the driver and server. This PR corrects an issue that never made it to a release but we would like to take the opportunity to re-highlight what each of these properties mean.
cursor.closed-cursor.close()has been called, and there are no more documents stored in the cursor.cursor.killed-cursor.close()was called while the cursor still had a non-zero id, and the driver sent a killCursors command to free server-side resourcescursor.id == null- The cursor has yet to send it's first command (ex.find,aggregate)cursor.id.isZero()- The server sent the driver a cursor id of0indicating a cursor no longer exists on the server side because all data has been returned to the driver.cursor.bufferedCount()- The amount of documents stored locally in the cursor.
Features
- NODE-5718: add ReadConcernMajorityNotAvailableYet to retryable errors (#4154) (4f32dec)
- NODE-5801: allow multiple providers providers per type (#4137) (4d209ce)
- NODE-5853: support delegated KMIP data key option (#4129) (aa429f8)
- NODE-6136: parse cursor responses on demand (#4112) (3ed6a2a)
- NODE-6157: add signature to github releases (#4119) (f38c5fe)
Bug Fixes
- NODE-5801: use more specific key typing for multiple KMS provider support (#4146) (465ffd9)
- NODE-6085: add TS support for KMIP data key options (#4128) (f790cc1)
- NODE-6241: allow
Binaryas local KMS provider key (#4160) (fb724eb) - NODE-6242: close becomes true after calling close when documents still remain (#4161) (e3d70c3)
Documentation
We invite you to try the mongodb library immediately, and report any issues to the NODE project.
v6.7.0
6.7.0 (2024-05-29)
The MongoDB Node.js team is pleased to announce version 6.7.0 of the mongodb package!
Release Notes
Support for MONGODB-OIDC Authentication
MONGODB-OIDC is now supported as an authentication mechanism for MongoDB server versions 7.0+. The currently supported facets to authenticate with are callback authentication, human interaction callback authentication, Azure machine authentication, and GCP machine authentication.
Azure Machine Authentication
The MongoClient must be instantiated with authMechanism=MONGODB-OIDC in the URI or in the client options. Additional required auth mechanism properties of TOKEN_RESOURCE and ENVIRONMENT are required and another optional username can be provided. Example:
const client = new MongoClient('mongodb+srv://<username>@<host>:<port>/?authMechanism=MONGODB-OIDC&authMechanismProperties=TOKEN_RESOURCE:<azure_token>,ENVIRONMENT:azure');
await client.connect();GCP Machine Authentication
The MongoClient must be instantiated with authMechanism=MONGODB-OIDC in the URI or in the client options. Additional required auth mechanism properties of TOKEN_RESOURCE and ENVIRONMENT are required. Example:
const client = new MongoClient('mongodb+srv://<host>:<port>/?authMechanism=MONGODB-OIDC&authMechanismProperties=TOKEN_RESOURCE:<gcp_token>,ENVIRONMENT:gcp');
await client.connect();Callback Authentication
The user can provide a custom callback to the MongoClient that returns a valid response with an access token. The callback is provided as an auth mechanism property an has the signature of:
const oidcCallBack = (params: OIDCCallbackParams): Promise<OIDCResponse> => {
// params.timeoutContext is an AbortSignal that will abort after 30 seconds for non-human and 5 minutes for human.
// params.version is the current OIDC API version.
// params.idpInfo is the IdP info returned from the server.
// params.username is the optional username.
// Make a call to get a token.
const token = ...;
return {
accessToken: token,
expiresInSeconds: 300,
refreshToken: token
};
}
const client = new MongoClient('mongodb+srv://<host>:<port>/?authMechanism=MONGODB-OIDC', {
authMechanismProperties: {
OIDC_CALLBACK: oidcCallback
}
});
await client.connect();For callbacks that require human interaction, set the callback to the OIDC_HUMAN_CALLBACK property:
const client = new MongoClient('mongodb+srv://<host>:<port>/?authMechanism=MONGODB-OIDC', {
authMechanismProperties: {
OIDC_HUMAN_CALLBACK: oidcCallback
}
});
await client.connect();Fixed error when useBigInt64=true was set on Db or MongoClient
Fixed an issue where when setting useBigInt64=true on MongoClients or Dbs an internal function compareTopologyVersion would throw an error when encountering a bigint value.
Features
Bug Fixes
Documentation
We invite you to try the mongodb library immediately, and report any issues to the NODE project.
v6.6.2
6.6.2 (2024-05-15)
The MongoDB Node.js team is pleased to announce version 6.6.2 of the mongodb package!
Release Notes
Server Selection performance regression due to incorrect RTT measurement
Starting in version 6.6.0, when using the stream server monitoring mode, heartbeats were incorrectly timed as having a duration of 0, leading to server selection viewing each server as equally desirable for selection.
Bug Fixes
Documentation
We invite you to try the mongodb library immediately, and report any issues to the NODE project.
v6.6.1
6.6.1 (2024-05-06)
The MongoDB Node.js team is pleased to announce version 6.6.1 of the mongodb package!
Release Notes
ref()-ed timer keeps event loop running until client.connect() resolves
When the MongoClient is first starting up (client.connect()) monitoring connections begin the process of discovering servers to make them selectable. The ref()-ed serverSelectionTimeoutMS timer keeps Node.js' event loop running as the monitoring connections are created. In the last release we inadvertently unref()-ed this initial timer which would allow Node.js to close before the monitors could create connections.
Bug Fixes
Documentation
We invite you to try the mongodb library immediately, and report any issues to the NODE project.
v6.6.0
6.6.0 (2024-05-02)
The MongoDB Node.js team is pleased to announce version 6.6.0 of the mongodb package!
Release Notes
Aggregation pipelines can now add stages manually
When creating an aggregation pipeline cursor, a new generic method addStage() has been added in the fluid API for users to add aggregation pipeline stages in a general manner.
const documents = await users.aggregate().addStage({ $project: { name: true } }).toArray();Thank you @prenaissance for contributing this feature!
cause and package name included for MongoMissingDependencyErrors
MongoMissingDependencyErrors now include a cause and a dependencyName field, which can be used to programmatically determine which package is missing and why the driver failed to load it.
For example:
MongoMissingDependencyError: The iHateJavascript module does not exist
at findOne (mongodb/main.js:7:11)
at Object.<anonymous> (mongodb/main.js:14:1)
... 3 lines matching cause stack trace ...
at Module._load (node:internal/modules/cjs/loader:1021:12) {
dependencyName: 'iHateJavascript',
[Symbol(errorLabels)]: Set(0) {},
[cause]: Error: Cannot find module 'iHateJavascript'
Require stack:
- mongodb/main.js
at require (node:internal/modules/helpers:179:18)
at findOne (mongodb/main.js:5:5)
at Object.<anonymous> (mongodb/main.js:14:1) {
code: 'MODULE_NOT_FOUND',
requireStack: [ 'mongodb/main.js' ]
}
}
ServerDescription Round Trip Time (RTT) measurement changes
(1) ServerDescription.roundTripTime is now a moving average
Previously, ServerDescription.roundTripTime was calculated as a weighted average of the most recently observed heartbeat duration and the previous duration. This update changes this behaviour to average ServerDescription.roundTripTime over the last 10 observed heartbeats. This should reduce the likelihood that the selected server changes as a result of momentary spikes in server latency.
(2) Added minRoundTripTime to ServerDescription
A new minRoundTripTime property is now available on the ServerDescription class which gives the minimum RTT over the last 10 heartbeats. Note that this value will be reported as 0 when fewer than 2 samples have been observed.
type supported in SearchIndexDescription
It is now possible to specify the type of a search index when creating a search index:
const indexName = await collection.createSearchIndex({
name: 'my-vector-search-index',
// new! specifies that a `vectorSearch` index is created
type: 'vectorSearch',
definition: {
mappings: { dynamic: false }
}
});Collection.findOneAndModify's UpdateFilter.$currentDate no longer throws on collections with limited schema
Example:
// collection has no schema
collection.update(
$currentData: {
lastModified: true
} // no longer throws a TS error
);TopologyDescription now properly stringifies itself to JSON
The TopologyDescription class is exposed by the driver in server selection errors and topology monitoring events to provide insight into the driver's current representation of the server's topology and to aid in debugging. However, the TopologyDescription uses Maps internally, which get serialized to {} when JSON stringified. We recommend using Node's util.inspect() helper to print topology descriptions because inspect properly handles all JS types and all types we use in the driver. However, if JSON must be used, the TopologyDescription now provides a custom toJSON() hook:
client.on('topologyDescriptionChanged', ({ newDescription }) => {
// recommended!
console.log('topology description changed', inspect(newDescription, { depth: Infinity, colors: true }))
// now properly prints the entire topology description
console.log('topology description changed', JSON.stringify(newDescription))
});Omit readConcern and writeConcern in Collection.listSearchIndexes options argument
Important
readConcern and writeConcern are no longer viable keys in the options argument passed into Collection.listSearchIndexes
This type change is a correctness fix.
Collection.listSearchIndexes is an Atlas specific method, and Atlas' search indexes do not support readConcern and writeConcern options. The types for this function now reflect this functionality.
Don't throw error when non-read operation in a transaction has a ReadPreferenceMode other than 'primary'
The following error will now only be thrown when a user provides a ReadPreferenceMode other than primary and then tries to perform a command that involves a read:
new MongoTransactionError('Read preference in a transaction must be primary');Prior to this change, the Node Driver would incorrectly throw this error even when the operation does not perform a read.
Note: a RunCommandOperation is treated as a read operation for this error.
TopologyDescription.error type is MongoError
Important
The TopologyDescription.error property type is now MongoError rather than MongoServerError.
This type change is a correctness fix.
Before this change, the following errors that were not instances of MongoServerError were already passed into TopologyDescription.error at runtime:
MongoNetworkError(excludingMongoNetworkRuntimeError)MongoErrorwith aMongoErrorLabel.HandshakeErrorlabel
indexExists() no longer supports the full option
The Collection.indexExists() helper supported an option, full, that modified the internals of the method. When full was set to true, the driver would always return false, regardless of whether or not the index exists.
The full option is intended to modify the return type of index enumeration APIs (Collection.indexes() and Collection.indexInformation(), but since the return type of Collection.indexExists() this option does not make sense for the Collection.indexExists() helper.
We have removed support for this option.
indexExists(), indexes() and indexInformation() support cursor options in Typescript
These APIs have supported cursor options at runtime since the 4.x version of the driver, but our Typescript has incorrectly omitted cursor options from these APIs.
Index information helpers have accurate Typescript return types
Collection.indexInformation(), Collection.indexes() and Db.indexInformation() are helpers that return index information for a given collection or database. These helpers take an option, full, that configures whether the return value contains full index descriptions or a compact summary:
collection.indexes({ full: true }); // returns an array of index descriptions
collection.indexes({ full: false }); // returns an object, mapping index names to index keysHowever, the Typescript return type of these helpers was always Document. Thanks to @prenaissance, these helpers now have accurate type information! The helpers return a new type, IndexDescriptionCompact | IndexDescriptionInfo[], which accurately reflects the return type of these helpers. The helpers also support type narrowing by providing a boolean literal as an option to the API:
collection.indexes(); // returns `IndexDescriptionCompact | IndexDescriptionInfo[]`
collection.indexes({ full: false }); // returns an `IndexDescriptionCompact`
collection.indexes({ full: true }); // returns an `IndexDescriptionInfo[]`
collection.indexInfo(); // returns `IndexDescriptionCompact | IndexDescriptionInfo[]`
collection.indexInfo({ full: false }); // returns an `IndexDescriptionCompact`
collection.indexInfo({ full: true }); // returns an `IndexDescriptionInfo[]`
db.indexInfo(); // returns `IndexDescriptionCompact | IndexDescriptionInfo[]`
db.indexInfo({ full: false }); // returns an `IndexDescriptionCompact`
db.indexInfo({ full: true }); // returns an `IndexDescriptionInfo[]`AWS credentials with expirations no longer throw when using on-demand AWS KMS credentials
In addition to letting users provide KMS credentials manually, client-side encryption supports fetching AWS KMS credentials on-demand using the AWS SDK. However, AWS credential mechanisms that returned access keys with expiration timestamps caused the driver to throw an error.
The driver will no longer throw an error when receiving an expiration token from the AWS SDK.
ClusterTime interface signature optionality
The ClusterTime interface incorrectly reported the signature field as required, the server may omit it, so the typescript has been updated to reflect reality.
Summary
Features
- NODE-3639: add a general stage to the aggregation pipeline builder (#4079) (8fca1aa)
- NODE-5678: add options parsing support for
timeoutMSanddefaultTimeoutMS(#4068) (ddd1e81) - NODE-5762: include
causeand package name for allMongoMissingDependencyErrors (#4067) (62ea94b) - NODE-5825: add
minRoundTripTimetoServerDescriptionand changeroundTripTimeto a moving average ([#40...
Contributors
Assets 2
v6.5.0
6.5.0 (2024-03-11)
The MongoDB Node.js team is pleased to announce version 6.5.0 of the mongodb package!
Release Notes
Bulk Write Operations Generate Ids using pkFactory
When performing inserts, the driver automatically generates _ids for each document if there is no _id present. By default, the driver generates ObjectIds. An option, pkFactory, can be used to configure the driver to generate _ids that are not object ids.
For a long time, only Collection.insert and Collection.insertMany actually used the pkFactory, if configured. Notably, Collection.bulkWrite(), Collection.initializeOrderedBulkOp() and Collection.initializeOrderedBulkOp() always generated ObjectIds, regardless of what was configured on collection.
The driver always generates _ids for inserted documents using the pkFactory.
Caution
If you are using a pkFactory and performing bulk writes, you may have inserted data into your database that does not have _ids generated by the pkFactory.
Fixed applying read preference to commands depending on topology
When connecting to a secondary in a replica set with a direct connection, if a read operation is performed, the driver attaches a read preference of primaryPreferred to the command.
Fixed memory leak in Connection layer
The Connection class has recently been refactored to operate on our socket operations using promises. An oversight how we made async network operations interruptible made new promises for every operation. We've simplified the approach and corrected the leak.
Query SRV and TXT records in parallel
When connecting using a convenient SRV connection string (mongodb+srv://) hostnames are obtained from an SRV dns lookup and some configuration options are obtained from a TXT dns query. Those DNS operations are now performed in parallel to reduce first-time connection latency.
Container and Kubernetes Awareness
The Node.js driver now keeps track of container metadata in the client.env.container field of the handshake document.
If space allows, the following metadata will be included in client.env.container:
env?: {
container?: {
orchestrator?: 'kubernetes' // if process.env.KUBERNETES_SERVICE_HOST is set
runtime?: 'docker' // if the '/.dockerenv' file exists
}
}
Note: If neither Kubernetes nor Docker is present, client.env will not have the container property.
Add property errorResponse to MongoServerError
The MongoServer error maps keys from the error document returned by the server on to itself. There are some use cases where the original error document is desirable to obtain in isolation. So now, the mongoServerError.errorResponse property stores a reference to the error document returned by the server.
Deprecated unused CloseOptions interface
The CloseOptions interface was unintentionally made public and was only intended for use in the driver's internals. Due to recent refactoring (NODE-5915), this interface is no longer used in the driver. Since it was marked public, out of an abundance of caution we will not be removing it outside of a major version, but we have deprecated it and will be removing it in the next major version.
Features
- NODE-5968: container and Kubernetes awareness in client metadata (#4005) (28b7040)
- NODE-5988: Provide access to raw results doc on MongoServerError (#4016) (c023242)
- NODE-6008: deprecate CloseOptions interface (#4030) (f6cd8d9)
Bug Fixes
- NODE-5636: generate _ids using pkFactory in bulk write operations (#4025) (fbb5059)
- NODE-5981: read preference not applied to commands properly (#4010) (937c9c8)
- NODE-5985: throw Nodejs' certificate expired error when TLS fails to connect instead of
CERT_HAS_EXPIRED(#4014) (057c223) - NODE-5993: memory leak in the
Connectionclass (#4022) (69de253)
Performance Improvements
Documentation
We invite you to try the mongodb library immediately, and report any issues to the NODE project.
v6.4.0
6.4.0 (2024-02-29)
The MongoDB Node.js team is pleased to announce version 6.4.0 of the mongodb package!
Release Notes
Server selection will use a different Mongos on retry
When retrying reads or writes on a sharded cluster, the driver will attempt to select a different mongos for the retry if multiple are present. This should heuristically avoid encountering the original error that caused the need to retry the operation.
Caching AWS credentials provider per client
Instead of creating a new AWS provider for each authentication, we cache the AWS credentials provider per client to prevent overwhelming the auth endpoint and ensure that cached credentials are not shared with other clients.
BSON upgraded to ^6.4.0
BSON has had a number of performance increases in the last two releases (6.3.0 and 6.4.0). Small basic latin (ASCII) only strings, small memory allocations (ObjectId and Decimal128) and numeric parsing operations (int32, doubles, and longs) have all had optimizations applied to them.
For details check out the release notes here: BSON 6.3.0 and BSON 6.4.0 🐎
ExceededTimeLimit was made a retryable reads error
Read operations will be retried after receiving an error with the ExceededTimeLimit label.
Fixed unresolved request issue in KMS requester
Internal to the field-level encryption machinery is a helper that opens a TLS socket to the KMS provider endpoint and submits a KMS request. The code neglected to add a 'close' event listener to the socket, which had the potential to improperly leave the promise pending indefinitely if no error was encountered.
The base64 padding is now preserved in the saslContinue command
The authentication was rejected by the saslContinue command from mongosh due to missing "=" padding from the client. We fixed the way we parse payload to preserve trailing "="s.
countDocuments now types the filter using the collection Schema
Previously, countDocuments had a weakly typed Document type for the filter allowing any JS object as input. The filter is now typed as Filter<Schema> to enable autocompletion, and, hopefully, catch minor bugs.
Thank you to @pashok88895 for contributing to this improvement.
The type error with $addToSet in bulkWrite was fixed
Previously the following code sample would show a type error:
interface IndexSingatureTestDocument extends Document {
readonly myId: number;
readonly mySet: number[];
}
const indexSingatureCollection = undefined as unknown as Collection<IndexSingatureTestDocument>;
indexSingatureCollection.bulkWrite([
{
updateOne: {
filter: { myId: 0 },
update: {
$addToSet: { mySet: 0 } // The type error! Type 'number' is not assignable to type 'never'.
}
}
}
]);It happened because the driver's Document type falls back to any, and internally we could not distinguish whether or not this assignment was intentional and should be allowed.
After this change, users can extend their types from Document/any, or use properties of any type and we skip the $addToSet validation in those cases.
Fixed heartbeat duration including socket creation
The ServerHeartbeatSucceeded and ServerHeartbeatFailed event have a duration property that represents the time it took to perform the hello handshake with MongoDB. The Monitor responsible for issuing heartbeats mistakenly included the time it took to create the socket in this field, which inflates the value with the time it takes to perform a DNS lookup, TCP, and TLS handshakes.
Errors on cursor transform streams are now properly propagated.
These were previously swallowed and now will be emitted on the error event:
const transform = new Transform({
transform(data, encoding, callback) {
callback(null, data);
},
});
const stream = db.collection('tests').find().sort({ studentId: -1 }).stream({ transform });
stream.on('error', err => {
// The error will properly be emitted here.
});The AWS token is now optional
Users may provide an AWS_SESSION_TOKEN as a client option or AWS configuration in addition to a username and password. But if the token is not provided, the driver won't throw an exception and let AWS SDK handle the request.
Features
- NODE-3449: Add serverConnectionId to Command Monitoring Spec (735f7aa)
- NODE-3470: retry selects another mongos (#3963) (84959ee)
- NODE-3689: require hello command for connection handshake to use OP_MSG disallowing OP_QUERY (#3938) (ce7df0f)
- NODE-5717: make ExceededTimeLimit retryable reads error (#3947) (106ab09)
- NODE-5939: Implement 6.x: cache the AWS credentials provider in the MONGODB-AWS auth logic (#3991) (e0a37e5)
- NODE-5978: upgrade BSON to
^6.4.0(#4007) (90f2f70)
Bug Fixes
- NODE-5127: implement reject kmsRequest on server close (#3964) (568e05f)
- NODE-5609: node driver omits base64 padding in sasl-continue command (#3975) (b7d28d3)
- NODE-5765: change type for countDocuments (#3932) (22cae0f)
- NODE-5791: type error with $addToSet in bulkWrite (#3953) (b93d405)
- NODE-5840: heartbeat duration includes socket creation (#3973) (a42039b)
- NODE-5901: propagate errors to transformed stream in cursor (#3985) (ecfc615)
- NODE-5944: make AWS session token optional (#4002) (f26de76)
Performance Improvements
- NODE-5771: improve new connection (#3948) (a4776cf)
- NODE-5928: consolidate signal use and abort promise wrap (#3992) (38742c2)
Documentation
We invite you to try the mongodb library immediately, and report any issues to the NODE project.
Contributors
Assets 2
v5.9.2
5.9.2 (2023-11-16)
The MongoDB Node.js team is pleased to announce version 5.9.2 of the mongodb package!
Release Notes
Fix connection leak when serverApi is enabled
When enabling serverApi the driver's RTT mesurment logic (used to determine the closest node) still sent the legacy hello command "isMaster" causing the server to return an error. Unfortunately, the error handling logic did not correctly destroy the socket which would cause a leak.
Both sending the correct hello command and the error handling connection clean up logic are fixed in this change.
Bug Fixes
Documentation
We invite you to try the mongodb library immediately, and report any issues to the NODE project.