lboka/doc-exports
1
0
Fork 0
forked from docs/doc-exports
Code Pull Requests Activity
doc-exports/docs/drs/umn/drs_15_0100.html
Ru, Li Yi 2ce446ea3c drs_umn_20240514 
Reviewed-by: Székely, Ond <ond.szekely@t-systems.com>
Co-authored-by: Ru, Li Yi <liyiru7@huawei.com>
Co-committed-by: Ru, Li Yi <liyiru7@huawei.com>
2024-07-30 11:03:03 +00:00

2.8 KiB
Raw Blame History

What Can I Do When OOM Occurs During the Migration from MongoDB to DDS?

Scenarios

Out of memory (OOM) occurs during the migration from MongoDB to DDS, causing migration failures.

Possible Cause

The possible causes are as follows:

  • If the mongod service of the source database is deployed on a single server, OOM occurs when the migration process consumes large amounts of memory through operations such as creating indexes and sorting queries.
  • If the mongod service is deployed on a server with other services and the cacheSizeGB value is not specified, OOM occurs when all available memory has been allocated to other services, so the WiredTiger engine does not have sufficient memory.

    By default, the memory used by the WiredTiger engine of mongod is calculated as follows: (Memory in GB-1 GB) x 50% for version 3.2 or (Memory in GB-1 GB) x 60% for version 3.4 and later.

Solution

  • If the mongod service is deployed on a single server, do not perform any operations that consume large amounts of memory during the migration.
  • If the mongod service and other services are deployed on the same server, set the value of cacheSizeGB to the half of the minimal idle memory to ensure that memory used in peak hours will not be allocated to WiredTiger excessively.
Parent topic: Real-Time Migration