Kernel Version Description
This section describes the kernel version updates of Document Database Service (DDS). This upgrade does not affect any functions or APIs.
Version |
Date |
Description |
---|---|---|
5.0 |
September 2024 |
|
August 2024 |
|
|
July 2024 |
|
Version |
Date |
Description |
---|---|---|
4.4 |
September 2024 |
|
August 2024 |
|
|
July 2024 |
|
|
June 2024 |
|
|
May 2024 |
|
|
April 2024 |
|
|
March 2024 |
Resolved the problem that fields output by setWindowFields are missing. |
|
February 2024 |
|
|
January 2024 |
Resolved the problem that there is a possibility that regular expression matching fails. |
|
December 2023 |
|
|
November 2023 |
Resolved the problem that the command output is not displayed on the memory monitoring page after a command is executed. |
|
October 2023 |
|
|
September 2023 |
|
|
August 2023 |
|
|
July 2023 |
|
|
May 2023 |
Added totalTimeProcessingMicros, processingMethod, totalTimeTruncatingMicros and truncateCount to oplogTruncation in serverStatus. |
|
April 2023 |
Optimized the transaction execution logic. |
|
March 2023 |
|
|
January 2023 |
|
|
November 2022 |
|
Version |
Date |
Description |
---|---|---|
4.2 |
September 2024 |
|
August 2024 |
|
|
July 2024 |
|
|
June 2024 |
|
|
May 2024 |
|
|
April 2024 |
Optimized the performance of distributed transactions in shard primary/standby switchover scenarios. |
|
March 2024 |
Supported the startAfter feature. |
|
February 2024 |
|
|
January 2024 |
Resolved the problem that there is a possibility that regular expression matching fails. |
|
December 2023 |
|
|
November 2023 |
Resolved the problem that the command output is not displayed on the memory monitoring page after a command is executed. |
|
October 2023 |
|
|
September 2023 |
|
|
August 2023 |
|
|
July 2023 |
|
|
June 2023 |
|
|
May 2023 |
Resolved the writeConcern error code matching issue after a primary/standby switchover. |
|
April 2023 |
|
|
March 2023 |
|
|
January 2023 |
|
|
November 2022 |
|
|
October 2022 |
|
|
September 2022 |
|
|
June 2022 |
|
Version |
Date |
Description |
---|---|---|
4.0 |
September 2024 |
|
August 2024 |
|
|
July 2024 |
|
|
June 2024 |
Supported mongo exporter. |
|
May 2024 |
None |
|
April 2024 |
None |
|
March 2024 |
None |
|
February 2024 |
Resolved the problem that geoNear is not displayed when explain() is executed. |
|
January 2024 |
Resolved the problem that there is a possibility that regular expression matching fails. |
|
December 2023 |
|
|
November 2023 |
None |
|
October 2023 |
|
|
September 2023 |
Optimized the resizeOplog logic. |
|
August 2023 |
|
|
July 2023 |
|
|
June 2023 |
|
|
May 2023 |
|
|
April 2023 |
|
|
March 2023 |
|
|
January 2023 |
|
|
November 2022 |
Fixed the bug that MongoDB Compass occasionally fails to be connected through SSL. |
|
October 2022 |
|
|
July 2022 |
|
|
June 2022 |
Supported the releaseFreeMemory command for mongos nodes. |
Version |
Date |
Description |
---|---|---|
3.4 |
September 2024 |
None |
August 2024 |
None |
|
July 2024 |
None |
|
June 2024 |
None |
|
May 2024 |
None |
|
April 2024 |
Optimized aggregate query and supported mapping adding for $project. |
|
March 2024 |
None |
|
February 2024 |
None |
|
January 2024 |
None |
|
December 2023 |
Restricted the permission to run a risky reIndex command. |
|
November 2023 |
None |
|
October 2023 |
Optimized the method for obtaining locks by running the ServerStatus command. |
|
September 2023 |
Displayed detailed slow query log information. |
|
August 2023 |
|
|
July 2023 |
Synchronized ReleaseFreeMemory to version 3.4. |
|
May 2023 |
|
|
April 2023 |
Fixed the bug that the activeSession on the standby config node in a cluster is not updated in a timely manner. |
|
March 2023 |
|
|
January 2023 |
|
|
October 2022 |
|
|
July 2022 |
Resolved the weak password verification issue. |
|
June 2022 |
Supported mongos log anonymization. |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot