ApsaraDB for MongoDB:Minor versions of ApsaraDB for MongoDB

Minor version

Release date

Benchmark version

Description

8.0.5

2024-09-03

7.0.14

• The benchmark version is upgraded to MongoDB 7.0.14 to fix WT-12708 issues. For more information about WT-12708, see Evaluation/Revision of eviction random traversal.

8.0.4

2024-06-17

7.0.10

• The benchmark version is upgraded to MongoDB 7.0.10 to fix issues concerning distributed transactions. For more information about the issues, see Sharded multi-document transactions may perform operations using inconsistent sharding metadata.

8.0.2

2024-01-24

7.0.3

• The following issue is fixed: A client in a Virtual Private Cloud (VPC) fails to connect to mongos nodes in the VPC.

8.0.1

2024-01-10

7.0.3

• Minor version compatibility is optimized and parameter settings that cannot be recognized are ignored.

• Account permissions are limited to avoid security risks caused by the creation of an account with excessive permissions.

• This minor version is the first official version of MongoDB 7.0.

Minor version

Release date

Benchmark version

Description

7.0.12

2024-09-03

6.0.17

• The benchmark version is upgraded to MongoDB 6.0.17 to fix WT-12708 issues. For more information about WT-12708, see Evaluation/Revision of eviction random traversal.

7.0.9

2024-06-06

6.0.15

• The benchmark version is upgraded to MongoDB 6.0.15 to fix issues concerning distributed transactions. For more information about the issues, see Sharded multi-document transactions may perform operations using inconsistent sharding metadata.

7.0.7

2024-03-12

6.0.13

• The performance of compact operations is improved and the failure rate of the operations is reduced.

7.0.6

2024-02-04

6.0.13

• The benchmark version is upgraded to MongoDB 6.0.13.

• Issues related to SERVER-78813 and SERVER-63865 are fixed.

7.0.5

2024-01-23

6.0.6

• The following issue is fixed: A client in a VPC fails to connect to mongos nodes in the VPC.

7.0.4

2024-01-10

6.0.6

• Minor version compatibility is optimized and parameter settings that cannot be recognized are ignored.

• Account permissions are limited to avoid security risks caused by the creation of an account with excessive permissions.

• Forward compatibility for internal account authentication is supported.

7.0.3

2023-07-13

6.0.6

• Routing issues with read-only nodes are fixed.

7.0.2

2023-06-12

6.0.6

• Bidirectional data synchronization is supported.

• The benchmark version is upgraded to MongoDB 6.0.6.

7.0.1

2023-01-06

6.0.3

• The runCommandOnShard command developed by Alibaba Cloud is added.

• The audit log feature is supported. For more information about how to enable the audit log feature, see Enable the audit log feature.

• The benchmark version is upgraded to MongoDB 6.0.3.

7.0.0

2022-11-02

6.0.0

• The following issue is fixed: The movePrimary command added in MongoDB 5.0 causes inconsistent shard metadata. For more information, see SERVER-68511.

• This minor version is the first official version of MongoDB 6.0.

Minor version

Release date

Benchmark version

Description

6.0.14

2024-08-03

5.0.28

• The benchmark version is upgraded to MongoDB 5.0.28.

• WT-12708 issues are fixed. For more information about WT-12708, see Evaluation/Revision of eviction random traversal.

6.0.13

2024-06-24

5.0.26

• The maximum number of connections during reloading can be modified.

• The benchmark version is upgraded to MongoDB 5.0.26 to fix issues concerning distributed transactions. For more information about the issues, see Sharded multi-document transactions may perform operations using inconsistent sharding metadata.

6.0.10

2024-02-06

5.0.24

• The benchmark version is upgraded to MongoDB 5.0.24.

• Issues related to SERVER-78813 and SERVER-63865 are fixed.

6.0.9

2024-01-23

5.0.21

• The following issue is fixed: A client in a VPC fails to connect to mongos nodes in the VPC.

6.0.8

2023-10-10

5.0.21

• The following issue is fixed: The system fails to start after the oplog size is changed.

• The benchmark version is upgraded to MongoDB 5.0.21.

6.0.7

2023-07-06

5.0.18

• Bidirectional data synchronization is supported.

• Routing issues with read-only nodes are fixed.

• The benchmark version is upgraded to MongoDB 5.0.18.

6.0.6

2023-02-09

5.0.14

• The following issue is fixed: The commands developed by Alibaba Cloud may cause null pointers.

6.0.5

2023-01-06

5.0.14

• The runCommandOnShard command developed by Alibaba Cloud is added.

• The issue of missing audit logs is fixed.

• The original commands are added to the slow query logs of a getMore operation. For more information, see getMore.

• The benchmark version is upgraded to MongoDB 5.0.14.

6.0.4

2022-10-18

5.0.6

• Data backup and restoration are accelerated.

6.0.3

2022-09-09

5.0.6

• The unit of the latency parameter for slow logs is modified to microseconds (us).

• The db.adminCommand({currentConn:1}) command is added.

6.0.2

2022-08-17

5.0.6

• The issue of inconsistent shard metadata is fixed. For more information, see SERVER-68511.

6.0.1

2022-06-14

5.0.6

• The limits on the number of ulimit processes on Elastic Compute Service (ECS) are fixed.

• Audit logs are supported.

• The benchmark version is upgraded to MongoDB 5.0.6.

6.0.0

2021-09-27

5.0.3

• This minor version is the first official version of MongoDB 5.0.

Minor version

Release date

Benchmark version

Description

5.0.15

2024-06-24

4.4.29

• The following issue is fixed: Some commands are not recorded in audit logs.

5.0.14

2024-05-23

4.4.29

• The benchmark version is upgraded to MongoDB 4.4.29 to fix issues concerning distributed transactions. For more information about the issues, see Sharded multi-document transactions may perform operations using inconsistent sharding metadata.

5.0.13

2024-02-01

4.4.28

• The benchmark version is upgraded to MongoDB 4.4.28.

• Issues related to SERVER-78813 and SERVER-63865 are fixed.

5.0.12

2024-01-23

4.4.18

• The following issue is fixed: A client in a VPC fails to connect to mongos nodes in the VPC.

5.0.11

2023-07-17

4.4.18

• Issues related to bidirectional data synchronization are fixed.

5.0.10

2023-07-13

4.4.18

• Routing issues with read-only nodes are fixed.

5.0.9

2023-05-08

4.4.18

• Bidirectional data synchronization is supported.

5.0.8

2023-01-17

4.4.18

• The benchmark version is upgraded to MongoDB 4.4.18.

5.0.7

2022-11-22

4.4.16

• The benchmark version is upgraded to MongoDB 4.4.16.

• The original commands are added to the slow query logs of a getMore operation. For more information, see getMore.

5.0.6

2022-10-18

4.4.1

• Data backup and restoration are accelerated.

5.0.5

2022-07-21

4.4.1

• The following issue is fixed: A deadlock occurs and the primary/secondary switchover fails when the primary node steps down. For more information, see SERVER-59226.

• The following issue is fixed: ApsaraDB for MongoDB exits when change streams are used to pull the oplogs of distributed transactions. For more information, see SERVER-53566.

5.0.3

2021-10-26

4.4.1

• The following issues are fixed:

  • In the event of high-frequency evictions, executing the compact statement causes ApsaraDB for MongoDB to crash and exit.

  • In the event of high-frequency evictions, long-running transactions cause deadlocks.

  Note

  For more information, see SERVER-50365 and SERVER-46876.

• The limits on the number of ulimit processes on ECS are fixed.

• Incremental backup dependencies: oplogstones information is added to the local.oplog.rs.stats() result.

• Audit logs are supported.

5.0.2

2021-01-28

4.4.1

• Log scrolling is supported.

5.0.1

2020-11-23

4.4.1

• This minor version is the first official version of MongoDB 4.4.

Minor version

Release date

Benchmark version

Description

4.0.27

2024-01-23

4.2.23

• The following issue is fixed: A client in a VPC fails to connect to mongos nodes in the VPC.

4.0.26

2023-07-17

4.2.23

• Routing issues with read-only nodes are fixed. The issues occur only in instances that use cloud disks.

4.0.25

2023-06-13

4.2.23

• The following issue is fixed: Dependent fields do not exist in incremental logs.

4.0.24

2023-05-06

4.2.23

• The following issue is fixed: The database engine version of an instance is not displayed in the ApsaraDB for MongoDB console.

4.0.23

2022-12-13

4.2.23

• The benchmark version is upgraded to MongoDB 4.2.23.

• The original commands are added to the slow query logs of a getMore operation. For more information, see getMore.

4.0.22

2022-11-02

4.2.13

• The following issue is fixed: No results are returned for the show tables statement if password-free access over Virtual Private Cloud (VPC) is enabled.

4.0.21

2022-05-18

4.2.13

• The following issue is fixed: A deadlock occurs when the main process gradually exits. For more information, see SERVER-59226.

4.0.20

2021-12-01

4.2.13

• The benchmark version is upgraded to MongoDB 4.2.13.

4.0.19

2021-08-31

4.2.10

• The following issue is fixed: ApsaraDB for MongoDB exits when change streams are used to pull the oplogs of distributed transactions. For more information, see SERVER-50769.

4.0.18

2021-06-25

4.2.10

• The maximum size of a whitelist file is set to 64 KB.

• The following issue is fixed: The whitelists fail to be refreshed when a large number of whitelists are configured.

4.0.17

2021-05-21

4.2.10

• The serverless kernel feature is merged.

4.0.16

2021-05-21

4.2.10

• Oplog replay optimization is supported.

4.0.15

2021-03-03

4.2.10

• The following issue is fixed: The client IP address in the audit log for the shard node is the IP address of the mongos node.

• ApsaraDB for MongoDB proactively detects the I/O value of each directory and sends them to the db.serverStatus() result.

4.0.14

2021-02-05

4.2.10

• The information of the primary and secondary roles is added to audit logs.

• The following issue is fixed: Slow queries are delayed because sessions are cleared by session cleanup threads. For more information, see SERVER-5287.

• The following issue is fixed: Hashed indexes cannot be used as shard keys because they are incorrectly marked as multi-key indexes. For more information, see SERVER-48471.

• The following issue is fixed: The client IP address is mistaken for the IP address of the control machine, which causes the client connection to be treated as an internal connection.

4.0.13

2020-12-28

4.2.10

• The following issue is fixed: Incompatibility is caused by the useNewUpsert option added to the aggregate command.

4.0.12

2020-12-16

4.2.10

• The benchmark version is upgraded to MongoDB 4.2.10.

• The following issue is fixed: The sleep period set for the Hash-Based Message Authentication Codes (HMAC) key monitoring thread is too long. For more information, see SERVER-52654.

4.0.11

2020-11-16

4.2.1

• The OpenSSL library is upgraded to 1.1.1.

• The following issue is fixed: The full synchronization process is interrupted when a negative number is returned for the count command. For more information, see SERVER-35050.

• The following issue is fixed: When a disk is full and write operations are attempted, a write lock occurs.

• The IPv6 access issue is fixed.

4.0.10

2020-10-29

4.2.1

• By default, throttling is enabled.

• The following issue is fixed: Secondary nodes crash and exit when the mapReduce command is run.

4.0.9

2020-08-04

4.2.1

• The IP addresses of both the client and mongos node are displayed in the audit logs of the shard node.

• The following issue is fixed: An error occurs on WiredTiger because the system.profile performance data collection fails to be created.

• The backup completion time can be obtained in the end-of-backup command.

4.0.8

2020-06-10

4.2.1

• The following issue is fixed: The dbGetmore protocol is not processed when password-free access over VPC is enabled.

4.0.7

2020-06-03

4.2.1

• The following issue is fixed: The mongos node may crash and exit when the client is disconnected.

4.0.6

2020-05-19

4.2.1

• The following issue is fixed: An error occurs when data is written to multiple instances at a time because the size of audit logs exceeds 16 MB.

• The config.collections collection cannot be modified. However, the sh.enableBalancing()/sh.disableBalancing() command can be run.

• Checkpoints are accelerated when a large number of collections exist. For more information, see WT-5042.

• The routing logic is optimized for the mongos node to reduce CPU utilization.

• The following issue is fixed: The runCommandOnShard command cannot be found when commands related to runCommandOnShard are run.

4.0.5

2020-02-12

4.2.1

• The following issue is fixed: Out-of-memory (OOM) errors may occur on both the primary and secondary nodes of an instance that has low specifications and runs MongoDB 4.2 when indexes are concurrently created.

4.0.4

2019-12-19

4.2.1

• The following issue is fixed: An error indicating an unauthorized getMore operation occasionally occurs when the VPC password-free access feature is enabled.

4.0.2

2019-11-23

4.2.1

• The following issue is fixed: The show tables command fails to be run when password-free access over VPC is enabled.

• The following issue is fixed: If replica set members are not initialized during startup, the ts secs too high error message is reported and therefore ApsaraDB for MongoDB exits.

4.0.1

2019-11-21

4.2.1

• This minor version is the first official version of MongoDB 4.2.

Minor version

Release date

Benchmark version

Description

3.0.41

2024-05-22

4.0.28

• The benchmark version is upgraded to MongoDB 4.0.28.

3.0.40

2024-04-19

4.0.13

• Issues related to SERVER-50365 are fixed.

3.0.39

2023-11-28

4.0.13

• The tcmallocReleaseRate parameter is supported to troubleshoot OOM errors.

3.0.38

2021-10-27

4.0.13

• The stability of ApsaraDB for MongoDB is enhanced.

3.0.37

2021-09-09

4.0.13

• The log file rotation feature is added for instances that use the DynamoDB protocol. One log file is up to 300 MB in size.

3.0.36

2021-07-22

4.0.13

• The steam feature is provided for instances that use the DynamoDB protocol. The Sort field is added.

3.0.35

2021-06-25

4.0.13

• The restrictions of NEW_IMAGE on the Sort field are removed for instances that use the DynamoDB protocol. Only the KEYS_ONLY restriction remains in force.

• Registration is added for the updateTable command is command.

3.0.34

2021-04-28

4.0.13

• The out-of-memory issue is fixed for instances that use the DynamoDB protocol.

• The empty index check is added.

3.0.33

2021-03-03

4.0.13

• The following issue is fixed: The client IP address in the audit log for the shard node is the IP address of the mongos node.

3.0.32

2021-02-05

4.0.13

• The information of the primary and secondary roles is added to audit logs.

• The following issue is fixed: Slow queries are delayed because sessions are cleared by session cleanup threads. For more information, see SERVER-52879 Periodic operation latency spikes every 5 minutes due to closing idle cached WT sessions.

• The if_not_exists function is optimized for instances that use the DynamoDB protocol.

• Persistent attribute-definition can be used on dynamo-admin.

3.0.31

2020-12-31

4.0.13

• The steam feature is provided for instances that use the DynamoDB protocol.

• The 1 MB limit is applicable to instances that use the DynamoDB protocol.

• The following issue is fixed: Parentheses are not supported in the KeyCondition expression.

• The following issue is fixed: LIST data types may be returned as SET data types.

• The precision issue of NUMBER data types is fixed.

• The following issue is fixed: ApsaraDB for MongoDB crashes when data is written to multiple instances at a time.

3.0.30

2020-08-18

4.0.13

• The scan feature is provided for instances that use the DynamoDB protocol.

• CursorCache-optimized paging is supported for instances that use the DynamoDB protocol to prevent many cursors from being opened when a getMore operation is performed.

• The scheduling mode of SLB is changed to the SCH algorithm.

• The following issue is fixed: Primary keys are often returned for projection expressions.

3.0.29

2020-08-04

4.0.13

• The IP addresses of both the client and mongos node are displayed in the audit logs of the shard node.

• The following issue is fixed: An out-of-memory error occurs when an ApsaraDB for MongoDB replica set instance that runs MongoDB 4.0 attempts to send a heartbeat to a removed node. For more information, see SERVER-44567 Reimplement CommandState destructors for v4.0.

3.0.28

2020-07-14

4.0.13

• Global secondary indexes are supported for instances that use the DynamoDB protocol.

• Dynamic modification of parameters is supported for instances that use the DynamoDB protocol.

• The following issue is fixed: ApsaraDB for MongoDB may crash and exit if the DescribeTable, BatchGetItem, and BatchWriteItem commands are run in multithreading scenarios.

• Pipeline optimization is merged. For more information, see SERVER-42756 $multiply operator may return with or w/o an error depending on whether pipeline optimisation is enabled.

• The listIndexes command can list inprogress index construction process. You can use it to check whether an index is being constructed.

3.0.27

2020-06-10

4.0.13

• The following issue is fixed: The dbGetmore protocol is not processed when password-free access over VPC is enabled.

3.0.26

2020-06-03

4.0.13

• Users are not allowed to modify the config.collections collection. However, users are allowed to run the sh.enableBalancing()/sh.disableBalancing() command.

• Checkpoints are accelerated when a large number of collections exist. For more information, see WT-5042 Reduce configuration parsing overhead from checkpoints.

• You can specify the timeout period for loading the config.chunks metadata collection.

3.0.25

2020-4-28

4.0.13

• The performance is optimized when a large number of collections start.

• DynamoDB compatibility phase 2 is supported.

• The following issue is fixed: An error occurs when data is written to multiple instances at a time because the size of audit logs exceeds 16 MB.

3.0.24

2020-4-15

4.0.13

• The routing logic is optimized for the mongos node to reduce CPU utilization.

3.0.23

2020-4-03

4.0.13

• The following issue is fixed: Secondary nodes crash and cannot be started. For more information, see SERVER-46466 Race with findAndModify retryable write and session migration.

• The enableCommand command can be used to disable or enable commands for connections.

3.0.21

2020-02-07

4.0.13

• DynamoDB compatibility phase 1 is supported.

3.0.20

2020-01-02

4.0.13

• The following issue is fixed: In MongoDB 4.0.7, the mergeByPBRT field is added to the requests sent by the mongos node to MongoDB. As a result, an error is reported when the mongos node that runs MongoDB 3.0.19 accesses MongoDB 3.0.18 or earlier and an aggregate operation is performed.

3.0.19

2019-12-04

4.0.13

• The benchmark version is upgraded to MongoDB 4.0.13.

3.0.18

2019-10-24

4.0.3

• A database with its name being or starting with_tmp cannot be created.

3.0.17

2019-10-17

4.0.3

• The following issue is fixed: Secondary nodes crash and fail to start because the SessionUpdateTracker::_updateSessionInfo function fails to be asserted.

3.0.15

2019-08-21

4.0.3

• The following issue is fixed: Transparent data encryption (TDE) keys are truncated when they are passed to WiredTiger because they contain special characters.

• The following issue is fixed: An error occurs when data is written to multiple instances at a time because the size of audit logs exceeds 16 MB.

3.0.13

2019-07-31

4.0.3

• TDE encryption is supported at the instance level and the collection level.

• Dynamic modification of connections is supported.

• The hostInfo command is allowed.

• The MongoDB Compass tool is supported.

• The MongoDB SERVER-37394 issue is fixed. For more information, see the SERVER-37394 Invariant failure deadline. =Date_t::max() or Invariant failure date.isFormattable().

3.0.12

2019-04-08

4.0.3

• The benchmark version is upgraded to MongoDB 4.0.3.

3.0.11

2019-03-08

4.0.0

• The IPv6 feature is supported.

• The vpcAuthMode parameter is added to enable or disable password-free access over VPC.

• The output of audit logs is improved. The following issue is fixed: No request data is found in audit logs when the DML statement is executed.

• The post-startup deadlock issue in edge cases is fixed.

• The default behavior of index creation is changed to creation in the background.

• Single-database restoration is supported

3.0.8

2018-12-21

4.0.0

• The password-free access over VPC feature is added.

3.0.7

2018-11-30

4.0.0

• The limit that common users cannot delete built-in accounts is added.

3.0.6

2018-11-01

4.0.0

• Whitelist-related issues are fixed.

3.0.5

2018-10-16

4.0.0

• The following issue is fixed: The args of command in audit logs is null.

• The following issue is fixed: JSON parsing fails because NumberInt(10) is contained in the audit log file.

• When the MoveChunk command is run on a sharded cluster instance, the sessionId field is displayed in the change record.

3.0.2

2018-09-25

4.0.0

• This minor version is the first official version of MongoDB 4.0.

Minor version

Release date

Description

1.1.13

2023-01-10

• The following issue is fixed: The sysInfoCollector component causes the mongod process to unexpectedly exit.

1.1.12

2020-06-03

• Users are not allowed to modify the config.collections collection. However, users are allowed to run the sh.enableBalancing()/sh.disableBalancing() command.

• The timeout period for loading the config.chunks metadata collection can be configured.

1.1.8

2019-07-25

• The background indexing feature of the open source MongoDB is incorporated.

• The hostInfo command can be run over external connections to obtain host-related information. For more information about hostInfo, see hostInfo.

1.1.7

2019-04-10

• The following issue is fixed: Secondary nodes crash and exit due to batch application of oplogs during primary/secondary synchronization.

1.1.6

2019-01-28

• Single-database restoration is supported

1.1.5

2018-09-25

• The following feature of the open source MongoDB is incorporated: The space is not reclaimed after the dropCollection command is run. For more information, see SERVER-31101 WT table not dropped after collection is dropped due to long-running OperationContext.

• Data cannot be written to the admin database of the sharded cluster instance.

• The dbAdmin permission on the local and config databases is added for the root user.

• The rs.printSlaveReplicationInfo command can be run and the db.printslave permission can be granted to users.

1.1.4

2018-08-07

• The feature to address failed full synchronization provided by the open source MongoDB is incorporated. For more information, see SERVER-31995 Logged initial sync statistics may exceed 16mb causing fassert.

• The nodes in the RECOVERING state are ignored in oplog synchronization to prevent excessive oplog collections.

• The autoIndexID parameter cannot be set to false.

1.1.3

2018-06-22

• The following issue is fixed: WT cache is stuck when the serverStatus command is run to obtain the checkpoint list.

• The limits on balancers for shard chunks are removed.

1.1.2

2018-05-14

• The oplogDeleteGuard command supports multiple data sources.

• The following issue is fixed: A request is sent to the primary node to perform a full oplog scan when the secondary node selects the synchronization source.

• The following issue is fixed: The system load is too high after WiredTiger IOPS is limited by Cgroup.

• The cleanupOrphaned command is available. For more information about the cleanupOrphaned command, see cleanupOrphaned.

1.1.0

2017-12-28

• The following feature is added: Redundant logs can be automatically removed when scrolling.

• The physical hot backup feature is supported. This feature is compatible with disk snapshots and the usage is not limited to file copy operations.

• The oplog magnification ratio is modified from 20 to 40.

1.0.9

2017-12-05

• The following issue is fixed: The MapReduce command fails to be run. For more information, see MapReduce failure: missing ) in parenthetical.

• Data can be written to the admin.system.users collection over external connections to implement data import over Data Transmission Service (DTS).

1.0.5

2017-11-08

• The following issue is fixed: A user cannot be created over a VIP connection.

Minor version

Release date

Description

0.5.3

2019-10-24

• This version is the latest version of an instance that runs MongoDB 3.2. You cannot update its minor version.

0.5.1

2019-07-25

• The background indexing feature of the open source MongoDB is incorporated.

• The hostInfo command can be run over external connections to obtain host-related information. For more information about hostInfo, see hostInfo.

0.5.0

2018-09-25

• Data cannot be written to the admin database when the database is in the Sharding state.

• The nodes in the RECOVERING state are ignored in oplog synchronization to prevent excessive oplog collections.

• The SSL feature is supported.

0.4.9

2018-06-22

• The following issue is fixed: WiredTiger cache eviction hangs when the db.serverStatus() command is run to query the instance status and obtain the checkpoint list.

• The limits on balancers for shard chunks are removed.

0.4.8

2018-05-14

• The following issue is fixed: A request is sent to the primary node to perform a full oplog scan when the secondary node selects the synchronization source.

• The following issue is fixed: The system load is too high after WiredTiger IOPS is limited by Cgroup.

• The following issue is fixed: The primary node crashes and exits when the rs.stepDown() command is run on a replica set instance. For more information about the rs.stepDown() command, see rs.stepDown().

• The cleanupOrphaned command is available. For more information about the cleanupOrphaned command, see cleanupOrphaned.

0.4.7

2017-11-17

• The global lock is not added for physical hot backup.

• The following issue is fixed: Cloud users are not synchronized during full synchronization after authentication is disabled.

0.4.6

2017-09-05

• The following feature is added: Multiple VIP groups can be configured with netvipGroup. The group of a visitor can be obtained based on the visitor VIP. Hybrid access to both classic network and VPC is supported.

• The exact optime is returned from the physical hot backup operation of WiredTiger. For more information about optime, see optime.

0.4.5

2017-08-17

• The following issue is fixed: An embedded account access error is reported due to modification of the rs.status() command.

0.4.4

2017-08-17

• The issue that causes RangeDeleter to exit is fixed. For more information, see RangeDeleter assert failed because of replication lag.

• The rs.status() command provides an API to obtain the primary/secondary latency.

• Slow requests are supported on the mongos node.

• Only slow requests are recorded in ParallelBatchWriteMode lock audit logs.

0.4.3

2017-07-06

• WiredTiger hot backup is optimized.

• The issue of determining a public VIP by using a CIDR block is fixed.

• When the db.adminCommand({features: 1}) command is run, a list of features developed by Alibaba Cloud is returned.

• The default values of the oplogDeleteGuardExpire and oplogSizeMulti parameters are modified.

0.4.2

2017-05-31

• The following issue is fixed: The server crashes and exits when a fast count is performed.

• The permissions to manage shard tags are granted to users.

0.4.1

2017-05-25

• RocksDB is upgraded to V5.3.3. The DeleteRange operation can be used to delete all keys within a range.

• WiredTiger is upgraded to V3.2.13.

• The audit log feature is supported on the mongos node.

0.4.0

2017-04-27

• The db.adminCommand({currentConn: 1}) command is available on the mongos node and mongod to list the network connection information of all clients.

• Audit log classification is optimized to allow audit log switches to be controlled in a finer-grained manner.

• The following issue is fixed: Mongod crashes and exits due to the multi-thread concurrent update of oplogDeleteGuard.

• The mongos node prohibits the deletion of admin databases over VIPs.

• The splitVector command is available.

0.3.9

2017-04-13

• The following issue is fixed: The lock granularity is high when the settings of a collection are modified by running the db.runCommand({collMod: $collection}) command.

0.3.8

2017-03-28

• The following issue is fixed: ApsaraDB for MongoDB crashes and exits when the mongos node fails to connect to the shard node.

• The error is ignored when an unrecognized configuration item is detected.

0.3.6

2017-02-23

• RocksDB is supported as the storage engine of an ApsaraDB for MongoDB instance.

• The WiredTiger hot backup feature is supported.

• The names of some parameters are modified to make them consistent with the ones in the configuration file and facilitate the control and modification of parameters.

0.3.4

2016-12-27

• Audit logs are redesigned to provide a unified API for all requests and count the request duration.

0.3.3

2016-12-15

• The issues related to double rollback are fixed.

• Filtering audit logs by node role is supported.

0.3.2

2016-11-29

• The following issue is fixed: Some private IP addresses are incorrectly identified as public IP addresses.

0.3.0

2016-10-31

• The following issue in MongoDB 3.2.10 is fixed: The WiredTiger cache is evicted.

0.2.9

2016-10-28

• To prevent security risks, the following commands are disabled:

  • cloneCollection: copies a collection.

  • copydbgetnonce: obtains a one-time password before the copydb command is run.

• The audit log of the ParallelBatchWriteMode lock is added to view the impact of the oplog replay lock on read and write operations.

• Compiling projects in macOS is supported.

• The following issue is fixed: An ApsaraDB for MongoDB instance cannot be connected when a whitelist in a VPC environment conflicts with a whitelist of the cluster.

0.2.8

2016-10-18

• The db.runCommand({compact: $collection}) command is available to compress the physical storage space of a collection in a specified database. You can determine whether to reclaim the storage space.

• The built-in account feature is supported on the mongos node.

• The read-only operations on the config database are performed on the mongos node, and the following commands are disabled:

  • sh.addShard(): adds a shard node.

  • sh.removeShard(): removes a shard node.

• Users can specify the number of internal connections.

• Users can specify the maximum oplog size to prevent the case where the physical space cannot be reclaimed due to excessive oplogs.

• VPC connections bypass the whitelist check performed by the management machine.

• The db.adminCommand({tcmallocRelease: 1}) command is added to release the free memory of Thread-Caching Malloc.

• The kernel allows an oplog to generate special fields to support BLS bidirectional synchronization.

0.2.7

2016-09-13

• Internal patches are merged based on MongoDB 3.2.9.

0.2.6

2016-09-07

• The IO hang detection logic is improved to prevent IO hang misjudgment and split-brain issues.

• Automatic expiration of the oplogDeleteGuard parameters is supported for self-protection of the kernel when the backup task is hung for a long time.

0.2.5

2016-08-26

• An incremental backup API is provided for subsequent support for incremental backup.

• The tcpBacklog parameter is supported to fix the following issue: The instance is misjudged as unavailable due to TCP queue overflow.

• Redhat 7u packaging is supported.

0.2.4

2016-07-06

• Adaptive oplog management is supported. An oplog can be deleted only after it is synchronized to all nodes.

• Users can set a retention timestamp for an oplog. The oplogs that exceed this timestamp is retained for incremental backup.

• The AliNLP plug-in analysis-aliws supports full-text search of Chinese characters.

0.2.3

2016-04-28

• The oplog size is automatically modified based on the oplogSizeMB parameter. For more information about oplogSizeMB, see oplogSizeMB.

• Operation logs and audit logs can automatically scroll.

• The issue with the logic of the enableMajorityReadConcern parameter is fixed.

0.2.2

2016-04-14

• IO hang detection is supported. When IO hang is detected, ApsaraDB for MongoDB terminates the heartbeat connection with other members.

• Audit log overheads are reduced.

• The following issue is fixed: The metadata of WiredTiger is not evicted from the cache, which causes the metadata to occupy the cache and a MongoDB deadlock.

• When localhost connections are used, the permissions of the built-in hostManager, clusterMonitor, and clusterManager roles are granted.

0.2.1

2016-03-28

• The performance issue for generating random numbers from /dev/urandom during authentication is fixed.

• The currentOp and listDatabases commands are often used for read-only operations. Local host connections bypass permission checks.