If you need to assign different permissions to employees in your enterprise to access your DRS resources, IAM is a good choice for fine-grained permissions management. IAM provides identity authentication, permissions management, and access control, helping you secure access to cloud resources.
+If you need to assign different permissions to employees in your enterprise to access your DRS resources, IAM is a good choice for fine-grained permissions management. IAM provides identity authentication, permissions management, and access control, helping you to have a secure access to cloud resources.
With IAM, you can use your cloud account to create IAM users for your employees, and assign permissions to the users to control their access to specific resources. For example, some software developers in your enterprise need to use DRS resources but must not delete DRS tasks or perform any high-risk operations. To achieve this result, you can create IAM users for the software developers and grant them only the permissions required for using DRS resources.
If your account does not need individual IAM users for permissions management, you may skip over this topic.
IAM can be used free of charge. You pay only for the resources in your cloud account. For more information about IAM, see IAM Service Overview.
diff --git a/docs/drs/umn/drs_01_0302.html b/docs/drs/umn/drs_01_0302.html index ea188f36..079035fe 100644 --- a/docs/drs/umn/drs_01_0302.html +++ b/docs/drs/umn/drs_01_0302.html @@ -71,6 +71,17 @@- Single DB instance
- Primary/Standby DB instance
To the cloud
+DDM->DDM
+DDM
+DDM
+Clusters
+From the cloud
MySQL->MySQL
@@ -201,6 +212,19 @@One-way sync
To the cloud
+DDM->DDM
+Not supported
+Not supported
+Supported
+One-way sync
+To the cloud
Oracle->PostgreSQL
@@ -327,9 +351,18 @@PostgreSQL->PostgreSQL
- PostgreSQL 9.4.x
- PostgreSQL 9.5.x
- PostgreSQL 9.6.x
- PostgreSQL 10.x
- PostgreSQL 11.x
- PostgreSQL 12.x
- PostgreSQL 13.x
- PostgreSQL 14.x
- PostgreSQL 9.4.x
- PostgreSQL 9.5.x
- PostgreSQL 9.6.x
- PostgreSQL 10.x
- PostgreSQL 11.x
- PostgreSQL 12.x
- PostgreSQL 13.x
- PostgreSQL 14.x
- PostgreSQL 15.x
- PostgreSQL 9.5.x
- PostgreSQL 9.6.x
- PostgreSQL 10.x
- PostgreSQL 11.x
- PostgreSQL 12.x
- PostgreSQL 13.x
- PostgreSQL 14.x
- PostgreSQL 9.5.x
- PostgreSQL 9.6.x
- PostgreSQL 10.x
- PostgreSQL 11.x
- PostgreSQL 12.x
- PostgreSQL 13.x
- PostgreSQL 14.x
- PostgreSQL 15.x
To the cloud
+DDM->DDM
+Based on the live network
+Based on the live network
To the cloud
@@ -354,7 +387,7 @@MySQL->Kafka
- MySQL 5.6.x
- MySQL 5.7.x
- MySQL 5.6.x
- MySQL 5.7.x
- MySQL 8.0.x
Kafka 0.11 or later
Supported
To the cloud
+DDM->DDM
+Supported
+Supported
+Supported
+To the cloud
Oracle->PostgreSQL
@@ -621,6 +665,17 @@Supported
To the cloud
+DDM->DDM
+Supported
+Supported
+Not supported
+To the cloud
Oracle->PostgreSQL
diff --git a/docs/drs/umn/drs_03_0035.html b/docs/drs/umn/drs_03_0035.html index 60a746ad..f87ad51c 100644 --- a/docs/drs/umn/drs_03_0035.html +++ b/docs/drs/umn/drs_03_0035.html @@ -4,16 +4,16 @@DRS processes synchronized objects and allows you to add rules for selected objects.
Filtering Data
- The filter criteria are met after the update. You need to continue the synchronization and perform the same update operation on the destination database. If no data is matched, the operation will be ignored, causing data inconsistency.
- The filter criteria are not met after the update. You need to continue the synchronization and perform the same update operation on the destination database.
- On the Processing Data page, set Processing Type to Data filtering.
- In the Object area, select the table to be processed.
- In the Filtering Criteria area, enter the filter criteria (only the part after WHERE in the SQL statement, for example, id=1), and click Verify.
- Each table has only one verification rule.
- Up to 500 tables can be filtered at a time.
- The filter expression cannot use the package, function, variable, or constant of a specific DB engine. It must comply with the general SQL standard. Enter the part following WHERE in the SQL statement (excluding WHERE and semicolons), for example, sid > 3 and sname like "G %". A maximum of 512 characters are allowed.
- In SQL statements for setting filter criteria, keywords must be enclosed in backquotes, and the value of datatime (including date and time) must be enclosed in single quotation marks, for example, `update` > '2022-07-13 00:00:00' and age >10.
- Filter criteria cannot be configured for large objects, such as CLOB, BLOB, and BYTEA.
- You are not advised to set filter criteria for fields of approximate numeric types, such as FLOAT, DECIMAL, and DOUBLE.
- Do not use fields containing special characters as a filter condition.
- You are not advised to use non-idempotent expressions or functions as data processing conditions, such as SYSTIMESTAMP and SYSDATE, because the returned result may be different each time the function is called.
- In the Object area of the Data filtering page, select the table to be processed.
- In the Filtering Criteria area, enter the filter criteria (only the part after WHERE in the SQL statement, for example, id=1), and click Verify.
- Each table has only one verification rule.
- Up to 500 tables can be filtered at a time.
- The filter expression cannot use the package, function, variable, or constant of a specific DB engine. It must comply with the general SQL standard. Enter the part following WHERE in the SQL statement (excluding WHERE and semicolons), for example, sid > 3 and sname like "G %". A maximum of 512 characters are allowed.
- In SQL statements for setting filter criteria, keywords must be enclosed in backquotes, and the value of datatime (including date and time) must be enclosed in single quotation marks, for example, `update` > '2022-07-13 00:00:00' and age >10.
- Filter criteria cannot be configured for large objects, such as CLOB, BLOB, and BYTEA.
- You are not advised to set filter criteria for fields of approximate numeric types, such as FLOAT, DECIMAL, and DOUBLE.
- Do not use fields containing special characters as a filter condition.
- You are not advised to use non-idempotent expressions or functions as data processing conditions, such as SYSTIMESTAMP and SYSDATE, because the returned result may be different each time the function is called.
- After the verification is successful, click Generate Processing Rule. The rule is displayed.
- Click Next.
Advanced Settings for Data Filtering
If you need to query an association table, you can use the advanced settings of data processing.
-- On the Processing Data page, set Processing Type to Data filtering.
- In the Object area, select the table to be processed.
- In the Filtering Criteria area, specify the filtering criteria, for example, id1 in (select id from db1.tab1 where id >=3 and id <10), and click Verify.
- Each table has only one verification rule.
- Up to 500 tables can be filtered at a time.
- The filter expression cannot use the package, function, variable, or constant of a specific DB engine. It must comply with the general SQL standard. Enter the part following WHERE in the SQL statement (excluding WHERE and semicolons), for example, sid > 3 and sname like "G %". A maximum of 512 characters are allowed.
- Filter criteria cannot be configured for large objects, such as CLOB, BLOB, and BYTEA.
- You are not advised to set filter criteria for fields of approximate numeric types, such as FLOAT, DECIMAL, and DOUBLE.
- Do not use fields containing special characters as a filter condition.
- You are not advised to use non-idempotent expressions or functions as data processing conditions, such as SYSTIMESTAMP and SYSDATE, because the returned result may be different each time the function is called.
- In the Object area of the Data filtering page, select the table to be processed.
- In the Filtering Criteria area, specify the filtering criteria, for example, id1 in (select id from db1.tab1 where id >=3 and id <10), and click Verify.-
- Each table has only one verification rule.
- Up to 500 tables can be filtered at a time.
- The filter expression cannot use the package, function, variable, or constant of a specific DB engine. It must comply with the general SQL standard. Enter the part following WHERE in the SQL statement (excluding WHERE and semicolons), for example, sid > 3 and sname like "G %". A maximum of 512 characters are allowed.
- Filter criteria cannot be configured for large objects, such as CLOB, BLOB, and BYTEA.
- You are not advised to set filter criteria for fields of approximate numeric types, such as FLOAT, DECIMAL, and DOUBLE.
- Do not use fields containing special characters as a filter condition.
- You are not advised to use non-idempotent expressions or functions as data processing conditions, such as SYSTIMESTAMP and SYSDATE, because the returned result may be different each time the function is called.
- After the verification is successful, click Generate Processing Rule. The rule is displayed.
- In the Advanced Settings area, specify the configuration condition and rule for the association table to help you filter data.
- In the Configuration Condition area, enter the association table information entered in 3.
Database Name, Table Name, Column Name, Primary Key, Index, and Filter Criteria are mandatory. If the table does not have an index, enter its primary key.
-Filter Criteria is the filter condition of the association table information entered in 3.
- - Then, click Verify.
- After the verification is successful, click Generate Configuration Rule. The rule is displayed in the Configuration Rule area.
To filter data in multiple association tables, repeat 5.
+ - After the verification is successful, click Generate Processing Rule. The rule is displayed.
- In the Advanced Settings area, specify the configuration condition and rule for the association table to help you filter data.
- In the Configuration Condition area, enter the association table information entered in 2.
Database Name, Table Name, Column Name, Primary Key, Index, and Filter Criteria are mandatory. If the table does not have an index, enter its primary key.
+Filter Criteria is the filter condition of the association table information entered in 2.
+ - Then, click Verify.
- After the verification is successful, click Generate Configuration Rule. The rule is displayed in the Configuration Rule area.
To filter data in multiple association tables, repeat 4.
Configuration rules can be deleted.
- In the Configuration Condition area, enter the association table information entered in 2.
- In the Configuration Condition area, enter the association table information entered in 3.
mongos Address
+mongos IP Address or Domain Name
IP address or domain name of the source database in the IP address/Domain name:Port format. The port of the source database. Range: 1 - 65535
You can enter a maximum of three groups of IP addresses or domain names of the source database. Separate multiple values with commas (,). For example: 192.168.0.1:8080,192.168.0.2:8080. Ensure that the entered IP addresses or domain names belong to the same sharded cluster.
@@ -285,7 +285,7 @@The username for accessing the source database.
mongos Password
+Database Password
The password for the database username.
Sharded Database
Enter the information about the sharded databases in the source database.
+If the source is a DDS instance, apply for an IP address for the shard node by referring to Document Database Service User Guide.
- On-premises database (PostgreSQL 9.4, 9.5, 9.6, 10, 11, 12, 13 and 14)
- ECS database (PostgreSQL 9.4, 9.5, 9.6, 10, 11, 12, 13 and 14)
- Other cloud database (PostgreSQL 9.4, 9.5, 9.6, 10, 11, 12, 13 and 14)
- RDS for PostgreSQL (9.5, 9.6, 10, 11, 12, 13 and 14)
- On-premises database (PostgreSQL 9.4, 9.5, 9.6, 10, 11, 12, 13, 14 and 15)
- ECS database (PostgreSQL 9.4, 9.5, 9.6, 10, 11, 12, 13, 14 and 15)
- Other cloud database (PostgreSQL 9.4, 9.5, 9.6, 10, 11, 12, 13, 14 and 15)
- RDS for PostgreSQL (9.5, 9.6, 10, 11, 12, 13, 14 and 15)
RDS for PostgreSQL (9.5, 9.6, 10, 11, 12, 13 and 14)
+RDS for PostgreSQL (9.5, 9.6, 10, 11, 12, 13, 14 and 15)
The major version of the destination database must be the same as or later than that of the source database.
From DDM to DDM
+Supported Source and Destination Databases
+Source DB + |
+Destination DB + |
+
|---|---|
|
+
|
+
Prerequisites
- You have logged in to the DRS console.
- For details about the DB types and versions supported by real-time synchronization, see Real-Time Synchronization.
Suggestions
- When a task is being started or in the full synchronization phase, do not perform DDL operations on the source database. Otherwise, the task may be abnormal.
- To keep data consistency before and after the synchronization, ensure that no data is written to the destination database during the synchronization.
- The success of database synchronization depends on environment and manual operations. To ensure a smooth synchronization, perform a synchronization trial before you start the synchronization to help you detect and resolve problems in advance.
- Start your synchronization task during off-peak hours. A less active database is easier to synchronize successfully. If the data is fairly static, there is less likely to be any severe performance impacts during the synchronization.
- If network bandwidth is not limited, the query rate of the source database increases by about 50 MB/s during full synchronization, and two to four CPUs are occupied.
- The data being synchronized may be locked by other transactions for a long period of time, resulting in read timeout.
- When DRS concurrently reads data from a database, it will use about 6 to 10 sessions. The impact of the connections on services must be considered.
- If you read a table, especially a large table, during the full migration, the exclusive lock on that table may be blocked.
- Data-Level Comparison
To obtain accurate comparison results, start data comparison at a specified time point during off-peak hours. If it is needed, select Start at a specified time for Comparison Time. Due to slight time difference and continuous operations on data, data inconsistency may occur, reducing the reliability and validity of the comparison results.
+
Precautions
Before creating a synchronization task, read the following notes:
+ +Type + |
+Restrictions + |
+
|---|---|
Database permissions + |
+
|
+
Synchronization object + |
+
|
+
Source database + |
+
|
+
Destination database + |
+
|
+
Precautions + |
+
|
+
Procedure
- On the Data Synchronization Management page, click Create Synchronization Task.
- On the Create Synchronization Instance page, specify the task name, description, and the synchronization instance details, and click Next.
- Task information description
++
+Table 3 Task and recipient description Parameter
+Description
+Region
+The region where the synchronization instance is deployed. You can change the region.
+Project
+The project corresponds to the current region and can be changed.
+Task Name
+The task name must start with a letter and consist of 4 to 50 characters. It can contain only letters, digits, hyphens (-), and underscores (_).
+Description
+The description consists of a maximum of 256 characters and cannot contain special characters !=<>'&"\
+ - Synchronization instance information
++
+Table 4 Synchronization instance settings Parameter
+Description
+Data Flow
+Select To the cloud.
+Source DB Engine
+Select DDM.
+Destination DB Engine
+Select DDM.
+Network Type
+The public network is used as an example. Available options: Public network, VPC, VPN or Direct Connect
+Destination DB Instance
+The DDM instance you created.
+Synchronization Instance Subnet
+Select the subnet where the synchronization instance is located. You can also click View Subnet to go to the network console to view the subnet where the instance resides.
+By default, the DRS instance and the destination DB instance are in the same subnet. You need to select the subnet where the DRS instance resides and ensure that there are available IP addresses. To ensure that the synchronization instance is successfully created, only subnets with DHCP enabled are displayed.
+Synchronization Mode
+- Full+Incremental
This synchronization mode allows you to synchronize data in real time. After a full synchronization initializes the destination database, an incremental synchronization parses logs to ensure data consistency between the source and destination databases.
+
NOTE:+If you select Full+Incremental, data generated during the full synchronization will be continuously synchronized to the destination database, and the source remains accessible.
+Source DB Instance Quantity
+Specifies the number of DB instances bound to the source DDM database. The default value is 2. The value ranges from 1 to 64. Set this parameter based on the site requirements.
+ - Full+Incremental
- Tags
++
+Table 5 Tags Parameter
+Description
+Tags
+- This setting is optional. Adding tags helps you better identify and manage your tasks. Each task can have up to 20 tags.
- After a task is created, you can view its tag details on the Tags tab. For details, see Tag Management.
- Task information description
+
- On the Configure Source and Destination Databases page, wait until the synchronization instance is created. Then, specify source and destination database information and click Test Connection for both the source and destination databases to check whether they have been connected to the synchronization instance. After the connection tests are successful, select the check box before the agreement and click Next.
+
+
+Table 6 Source database settings Parameter
+Description
+Middleware IP Address or Domain Name
+The IP address or domain name of the source DDM middleware.
+Port
+The port of the source DDM middleware. Value range: 1 to 65535
+Middleware Username
+The username of the source DDM instance.
+Middleware Password
+The password for the source DDM instance username.
+SSL Connection
+SSL encrypts the connections between the source and destination databases. If SSL is enabled, upload the SSL CA root certificate.
+NOTE:+- The maximum size of a single certificate file that can be uploaded is 500 KB.
- If the SSL certificate is not used, your data may be at risk.
DB Instance
+The sharded database details.
++ The IP address, domain name, username, and password of the source database are encrypted and stored in DRS, and will be cleared after the task is deleted.
++++
+Table 7 Destination database settings Parameter
+Description
+DB Instance Name
+The DDM instance you selected when you create a synchronization task. The instance name cannot be changed.
+Database Username
+The username for accessing the destination database.
+Database Password
+The database username and password are encrypted and stored in the system and will be cleared after the task is deleted.
+ - On the Set Synchronization Task page, select the objects to be synchronized, and then click Next.
+
+
+Table 8 Synchronization mode and object Parameter
+Description
+Incremental Conflict Policy
+The conflict policy refers to the conflict handling policy during incremental synchronization. By default, conflicts in the full synchronization phase are ignored.
+Synchronization Object
+Select Tables or Databases as required.
+If the synchronization objects in source and destination databases have different names, you can map the source object name to the destination one. For details, see Mapping Object Names.
+NOTE:+- To quickly select the desired database objects, you can use the search function.
- If there are changes made to the source databases or objects, click
in the upper right corner to update the objects to be synchronized.
- If the object name contains spaces, the spaces before and after the object name are not displayed. If there are multiple spaces between the object name and the object name, only one space is displayed.
- The name of the selected synchronization object cannot contain spaces.
- On the Check Task page, check the synchronization task.
- If any check fails, review the cause and rectify the fault. After the fault is rectified, click Check Again.
- If all check items are successful, click Next.+
You can proceed to the next step only when all checks are successful. If there are any items that require confirmation, view and confirm the details first before proceeding to the next step.
+
- On the displayed page, specify Start Time, confirm that the configured information is correct, and click Submit to submit the task.
+
+
+Table 9 Task startup settings Parameter
+Description
+Started Time
+Set Start Time to Start upon task creation or Start at a specified time based on site requirements.
+NOTE:+After a synchronization task is started, the performance of the source and destination databases may be affected. You are advised to start a synchronization task during off-peak hours.
+ - After the task is submitted, you can view and manage it on the Data Synchronization Management page.
- You can view the task status. For more information about task status, see Task Statuses.
- You can click
in the upper-right corner to view the latest task status.
+
You can create custom policies in either of the following ways:
- Visual editor: Select cloud services, actions, resources, and request conditions. This does not require knowledge of policy syntax.
- JSON: Create a policy in JSON format or edit the JSON strings of an existing policy.
For details about how to create a custom policy, see Identity and Access Management User Guide. The following describes examples of common DRS custom policies.
-Example Custom Policies
- Example 1: Allowing users to create DRS instances
{ +Example Custom Policies
- Example 1: Allowing users to create DRS migration instances
{ "Version": "1.1", "Statement": [{ - "Action": ["drs:instance:create"], + "Action": ["drs:migrationJob:create"], "Effect": "Allow" }] }- - Example 2: Denying DRS instance deletion
A policy with only "Deny" permissions must be used in conjunction with other policies to take effect. If the permissions assigned to a user contain both "Allow" and "Deny", the "Deny" permissions take precedence over the "Allow" permissions.
+ - Example 2: Denying DRS migration instance deletion
A policy with only "Deny" permissions must be used in conjunction with other policies to take effect. If the permissions assigned to a user contain both "Allow" and "Deny", the "Deny" permissions take precedence over the "Allow" permissions.
The following method can be used if you need to assign permissions of the DRS FullAccess policy to a user but you want to prevent the user from deleting DRS instances. Create a custom policy for denying DRS instance deletion, and attach both policies to the group to which the user belongs. Then, the user can perform all operations on DRS instances except deleting DRS instances. The following is an example of a deny policy:
{ "Version": "1.1", "Statement": [{ - "Action": ["drs:instance:delete"], + "Action": ["drs:migrationJob:delete"], "Effect": "Deny" }] }diff --git a/docs/drs/umn/drs_10_0402.html b/docs/drs/umn/drs_10_0402.html index 2d91df18..20c0ae31 100644 --- a/docs/drs/umn/drs_10_0402.html +++ b/docs/drs/umn/drs_10_0402.html @@ -2,7 +2,7 @@Importing Synchronization Objects
Real-time synchronization supports the import of objects through files. After a task is created, you can import object files on the Set Synchronization Task page.
- - Only Windows Microsoft Excel 97-2003 (*.xls), 2007, and later (*.xlsx) files can be imported. The downloaded compressed package provides the templates of the two versions.
- The file name can contain only spaces, letters, digits, hyphens (-), underscores (_), and parentheses.
- The format of the object information in the template must meet the requirements. The value is case-sensitive and cannot include angle brackets (<>), periods (.), and double quotation marks ("). Objects that start or end with a space are not supported.
- The task in the configuration supports table-level synchronization, database-level synchronization, or file import mode. Each time you switch to a new mode, the selected or imported database objects are cleared, and you need to select or import them again.
- If you want to import a file for mapping, fill in the first and second columns of the file based on the template. If the first two columns of a row are left blank, the row will be ignored.
- For the task created using the file import mode, database-level and table-level synchronization are not supported after the task is started.
- If you edit a task, the imported file must contain information about all objects. Importing only the updated objects is not allowed.
- If you edit a task again, the objects that have been synchronized cannot be mapped again. Ensure that the object names remain unchanged after the mapping.
- If you edit a task again, the exported object information is the synchronized object information.
- If the verification fails after the file is uploaded, click View Failure Details to download the error information.
- The object names entered in the Excel file must use the same letter case as the source object names.
- Only Windows Microsoft Excel 97-2003 (*.xls), 2007, and later (*.xlsx) files can be imported. The downloaded compressed package provides the templates of the two versions.
- The file name can contain only spaces, letters, digits, hyphens (-), underscores (_), and parentheses.
- The format of the object information in the template must meet the Excel file requirements. The database object names (such as the database name, schema name, or table name) in the file is case-sensitive and cannot include angle brackets (<>), periods (.), double quotation marks ("), and cannot start or end with a space.
- The task in the configuration supports table-level synchronization, database-level synchronization, or file import mode. Each time you switch to a new mode, the selected or imported database objects are cleared, and you need to select or import them again.
- If you want to import a file for mapping, fill in the first and second columns of the file based on the template. If the first two columns of a row are left blank, the row will be ignored.
- For the task created using the file import mode, database-level and table-level synchronization are not supported after the task is started.
- If you edit a task, the imported file must contain information about all objects. Importing only the updated objects is not allowed.
- If you edit a task again, the objects that have been synchronized cannot be mapped again. Ensure that the object names remain unchanged after the mapping.
- If you edit a task again, the exported object information is the synchronized object information.
- If the verification fails after the file is uploaded, click View Failure Details to download the error information.
- The object names entered in the Excel file must use the same letter case as the source object names.
Procedure
- On the Set Synchronization Task page, click Import object file in the Synchronization Object field.
- Click Download Template.
- Download the template and enter information about the objects to be imported.
- Click Select File. In the displayed dialog box, select the edited template.
- Click Upload.
- Example 1: Allowing users to create DRS migration instances
Failure cause: The source database version is not supported.
-Handling suggestion: Check whether the source database version is supported. Currently, only PostgreSQL 9.4, 9.5, 9.6, 10.0, 11.0, 12.0, 13.0, and 14.0 are supported.
+Handling suggestion: Check whether the source database version is supported. Currently, only PostgreSQL 9.4, 9.5, 9.6, 10.0, 11.0, 12.0, 13.0, 14.0, and 15.0 are supported.
Failure cause: The destination database version is not supported.
-Handling suggestion: Check whether the destination database version is supported. Currently, only PostgreSQL 9.5, 9.6, 10.0, 11.0, 12.0, 13.0, and 14.0 are supported.
+Handling suggestion: Check whether the destination database version is supported. Currently, only PostgreSQL 9.5, 9.6, 10.0, 11.0, 12.0, 13.0, 14.0, and 15.0 are supported.
Failure cause: The major versions of the source and destination databases must be the same and the minor version of the source database must be less than or equal to that of the destination database.
diff --git a/docs/drs/umn/drs_15_0100.html b/docs/drs/umn/drs_15_0100.html index 320de7a4..8a800e05 100644 --- a/docs/drs/umn/drs_15_0100.html +++ b/docs/drs/umn/drs_15_0100.html @@ -4,7 +4,7 @@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. diff --git a/docs/drs/umn/drs_change_history.html b/docs/drs/umn/drs_change_history.html index e774ec05..6f44e4f2 100644 --- a/docs/drs/umn/drs_change_history.html +++ b/docs/drs/umn/drs_change_history.html @@ -8,7 +8,19 @@
By default, the memory used by the WiredTiger engine of mongod is calculated as follows: (Memory in GB-1) x 50% for version 3.2 or (Memory in GB-1) x 60% for version 3.4 and later.
+- 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.
2024-04-15
+2024-06-11
+This issue is the seventeenth official release, which incorporates the following changes:
+- Modified Processing Data contents.
- Modified Importing Synchronization Objects contents.
- Supported real-time synchronization of PostgreSQL 15.
2024-05-20
+This issue is the sixteenth official release, which incorporates the following changes:
+- Supported real-time synchronization from DDM to DDM.
2024-04-15
This issue is the fifteenth official release, which incorporates the following changes:
- Supported Importing Synchronization Objects and Processing Data for real-time synchronization from MySQL to MySQL.