This topic describes how to use Data Transmission Service (DTS) to synchronize data from an ApsaraDB RDS for MySQL instance to an Elasticsearch cluster.
Prerequisites
An ApsaraDB RDS for MySQL instance is created. For more information, see Create an ApsaraDB RDS for MySQL instance.
An Elasticsearch cluster is created. For more information, see Create an Alibaba Cloud Elasticsearch cluster.
The available storage space of the Elasticsearch cluster is larger than the total size of the data in the ApsaraDB RDS for MySQL instance.
Precautions
Category | Description |
Limits on the source database |
|
Other limits |
|
Special cases | If the source database is a self-managed MySQL database, take note of the following items:
|
Billing
Synchronization type | Task configuration fee |
Schema synchronization and full data synchronization | Free of charge. |
Incremental data synchronization | Charged. For more information, see Billing overview. |
SQL operations that can be synchronized
Operation type | SQL statement |
DML | INSERT, UPDATE, and DELETE |
Permissions required for database accounts
Database | Required permission | References |
The source ApsaraDB RDS for MySQL instance | Read permissions on the objects to synchronize | Create an account on an ApsaraDB RDS for MySQL instance and Modify the permissions of a standard account on an ApsaraDB RDS for MySQL instance. |
The destination Elasticsearch cluster | The username (elastic by default) and the logon password that were set when the Elasticsearch cluster was created. |
If the source database account that you use is not created and authorized by using the ApsaraDB RDS for MySQL console, make sure that the account has the REPLICATION CLIENT, REPLICATION SLAVE, SHOW VIEW, and SELECT permissions.
Data type mappings
The data types of MySQL databases and Elasticsearch clusters do not have one-to-one correspondence. During initial schema synchronization, DTS converts the data types of the source database into the data types of the destination cluster. For more information, see Data type mappings for schema synchronization.
Term mappings
Elasticsearch | Relational database |
index | database |
type | table |
document | row |
field | column |
mapping | schema |
Procedure
- Go to the Data Synchronization Tasks page.
- Log on to the Data Management (DMS) console.
- In the top navigation bar, click DTS.
- In the left-side navigation pane, choose .
Note- Operations may vary based on the mode and layout of the DMS console. For more information, see Simple mode and Customize the layout and style of the DMS console.
- You can also go to the Data Synchronization Tasks page of the new DTS console.
- From the drop-down list to the right of Data Synchronization Tasks, select the region in which the data synchronization instance resides. Note If you use the new DTS console, you must select the region in which the data synchronization instance resides in the top navigation bar.
Click Create Task. On the page that appears, configure the source and destination databases.
Category
Parameter
Description
N/A
Task Name
The name of the task. DTS automatically assigns a name to the task. We recommend that you specify a descriptive name that makes it easy to identify the task. You do not need to specify a unique task name.
Source Database
Select an existing DMS database instance
The database instance that you want to use. You can choose whether to select an existing instance based on your business requirements.
If you select an existing instance, DTS automatically populates the parameters for the database.
If you do not select an existing instance, you must manually configure parameters for the database.
Database Type
The type of the destination instance. Select MySQL.
Access Method
The access method of the destination instance. Select Alibaba Cloud Instance.
Instance Region
Select the region where the source ApsaraDB RDS for MySQL instance resides.
Replicate Data Across Alibaba Cloud Accounts
Specifies whether data is synchronized across Alibaba Cloud accounts. In this example, No is selected.
RDS Instance ID
Select the ID of the source ApsaraDB RDS for MySQL instance.
Database Account
The database account of the source ApsaraDB RDS for MySQL instance. For information about the permissions that are required for the account, see the "Permissions required for database accounts" section of this topic.
Database Password
The password of the database account.
Encryption
Specifies whether to encrypt the connection to the database. Select Non-encrypted or SSL-encrypted based on your business requirements. If you select SSL-encrypted, you must enable SSL encryption for the ApsaraDB RDS for MySQL instance before you configure the data synchronization task. For more information, see Configure the SSL encryption feature.
Destination Database
Select an existing DMS database instance
The database instance that you want to use. You can choose whether to select an existing instance based on your business requirements.
If you select an existing instance, DTS automatically populates the parameters for the database.
If you do not select an existing instance, you must manually configure parameters for the database.
Database Type
The type of the destination database. Select Elasticsearch.
Access Method
The access method of the destination instance. Select Alibaba Cloud Instance.
Instance Region
The region in which the destination Elasticsearch cluster resides.
Instance ID
Select the ID of the destination Elasticsearch cluster.
Database Account
Enter the username that is used to connect to the Elasticsearch cluster. This account is the Username that you specified when you created the Elasticsearch cluster. The default database account in Elasticsearch clusters is elastic.
Database Password
The password of the database account.
- In the lower part of the page, click Test Connectivity and Proceed.
If the source or destination database is an Alibaba Cloud database instance, such as an ApsaraDB RDS for MySQL or ApsaraDB for MongoDB instance, DTS automatically adds the CIDR blocks of DTS servers to the whitelist of the instance. If the source or destination database is a self-managed database hosted on an Elastic Compute Service (ECS) instance, DTS automatically adds the CIDR blocks of DTS servers to the security group rules of the ECS instance, and you must ensure that the ECS instance can access the database. If the source or destination database is a self-managed database that is deployed in a data center or provided by a third-party cloud service provider, you must manually add the CIDR blocks of DTS servers to the whitelist of the database to allow DTS to access the database. For more information, see Add the CIDR blocks of DTS servers to the security settings of on-premises databases.
WarningIf the CIDR blocks of DTS servers are automatically or manually added to the whitelist of the database or instance, or to the ECS security group rules, security risks may arise. Therefore, before you use DTS to synchronize data, you must understand and acknowledge the potential risks and take preventive measures, including but not limited to the following measures: enhancing the security of your username and password, limiting the ports that are exposed, authenticating API calls, regularly checking the whitelist or ECS security group rules and forbidding unauthorized CIDR blocks, or connecting the database to DTS by using Express Connect, VPN Gateway, or Smart Access Gateway.
Configure objects to be synchronized and advanced settings.
Parameter
Description
Synchronization Types
By default, Incremental Data Synchronization is selected. You must also select Schema Synchronization and Full Data Synchronization. After the precheck is complete, DTS synchronizes the historical data of the selected objects from the source database to the destination cluster. The historical data is the basis for subsequent incremental synchronization.
Processing Mode of Conflicting Tables
Precheck and Report Errors: checks whether the destination database contains tables that have the same names as tables in the source database. If the source and destination databases do not contain tables that have identical table names, the precheck is passed. Otherwise, an error is returned during the precheck and the data synchronization task cannot be started.
NoteYou can use the object name mapping feature to rename the tables that are synchronized to the destination database. You can use this feature if the source and destination databases contain identical table names and the tables in the destination database cannot be deleted or renamed. For more information, see Map object names.
Ignore Errors and Proceed: skips the precheck for identical table names in the source and destination databases.
WarningIf you select Ignore Errors and Proceed, data inconsistency may occur, and your business may be exposed to potential risks.
If the source and destination databases have the same schemas, and a data record has the same primary key value as an existing data record in the destination database:
During full data synchronization, DTS does not synchronize the data record to the destination database. The existing data record in the destination database is retained.
During incremental data synchronization, DTS synchronizes the data record to the destination database. The existing data record in the destination database is overwritten.
If the source and destination databases have different schemas, data may fail to be initialized, only some columns are synchronized, or the data synchronization task fails. Operate with caution.
Precheck and Report Errors: checks whether the destination database contains collections that have the same names as collections in the source database. If the source and destination databases do not contain collections that have identical collection names, the precheck is passed. Otherwise, an error is returned during the precheck and the data synchronization task cannot be started.
NoteYou can use the object name mapping feature to rename the collections that are synchronized to the destination database. You can use this feature if the source and destination databases contain collections that have identical names and the collections in the destination database cannot be deleted or renamed. For more information, see Rename an object to be synchronized.
Ignore Errors and Proceed: skips the precheck for identical collection names in the source and destination databases.
WarningIf you select Ignore Errors and Proceed, data inconsistency may occur, and your business may be exposed to potential risks.
DTS does not synchronize data records that have the same primary key values as data records in the destination database.
Data may fail to be initialized, only some columns are synchronized, or the data synchronization task fails.
Precheck and Report Errors: checks whether the destination database contains tables that have the same names as tables in the source database. If the source and destination databases do not contain tables that have identical table names, the precheck is passed. Otherwise, an error is returned during the precheck and the data synchronization task cannot be started.
Ignore Errors and Proceed: skips the precheck for identical table names in the source and destination databases.
WarningIf you select Ignore Errors and Proceed, data inconsistency may occur, and your business may be exposed to potential risks.
If the source and destination databases have the same schemas, and a data record has the same primary key value as an existing data record in the destination database:
During full data synchronization, DTS does not synchronize the data record to the destination database. The existing data record in the destination database is retained.
During incremental data synchronization, DTS synchronizes the data record to the destination database. The existing data record in the destination database is overwritten.
If the source and destination databases have different schemas, data may fail to be initialized, only some columns are synchronized, or the data synchronization task fails. Operate with caution.
Index Name
If you select Table Name, the index created in the destination Elasticsearch cluster uses the same name as the table in the ApsaraDB RDS for MySQL instance.
If you select Database Name_Table Name, the index created in the destination Elasticsearch cluster is concatenated in the format of Database name_Table name.
Note The index name mapping rule takes effect for all tables.Capitalization of Object Names in Destination Instance
The capitalization of database names, table names, and column names in the destination instance. By default, DTS default policy is selected. You can select other options to ensure that the capitalization of object names is consistent with that in the source or destination database. For more information, see Specify the capitalization of object names in the destination instance.
Source Objects
Select one or more objects from the Source Objects section and click the icon to add the objects to the Selected Objects section.
NoteYou can select tables or databases as objects to synchronize. If you select tables as the objects to be synchronized, DTS does not synchronize other objects such as views, triggers, or stored procedures to the destination database.
Selected Objects
If you want to change the names of fields that are synchronized, you can click the name of the table to which the fields belong in the Selected Objects list, and specify the name of the index and the name of the index type in the Elasticsearch cluster for the table. After the configuration is complete, click OK. For more information, see Map object names.
NoteYou can specify SQL conditions to filter data. Only data that meets the specified conditions can be synchronized to the destination Elasticsearch cluster. For more information, see Use SQL conditions to filter data.
Click Next: Advanced Settings to configure advanced settings.
Parameter
Description
Select the dedicated cluster used to schedule the task
By default, DTS schedules the data synchronization task to the shared cluster if you do not specify a dedicated cluster. You can purchase a dedicated cluster of specified specifications to run DTS synchronization tasks. For more information, see What is a DTS dedicated cluster.
Set Alerts
Specifies whether to configure alerting for the data synchronization task. If the task fails or the synchronization latency exceeds the specified threshold, alert contacts will receive notifications. Valid values:
No: does not configure alerting.
Yes: configures alerting. In this case, you must also configure the alert threshold and alert contacts. For more information, see Configure monitoring and alerting when you create a DTS task.
Retry Time for Failed Connections
The retry time range for failed connections. If the source or destination database fails to be connected after the data synchronization task is started, DTS immediately retries a connection within the time range. Valid values: 10 to 1440. Unit: minutes. Default value: 720. We recommend that you set the parameter to a value greater than 30. If DTS reconnects to the source and destination databases within the specified time range, DTS resumes the data synchronization task. Otherwise, the data synchronization task fails.
NoteIf you set different retry time ranges for multiple DTS tasks that have the same source or destination database, the shortest retry time range that is set takes precedence.
When DTS retries a connection, you are charged for the DTS instance. We recommend that you specify the retry time range based on your business requirements. You can also release the DTS instance at your earliest opportunity after the source and destination instances are released.
The wait time before a retry when other issues occur in the source and destination databases.
The retry time range for other issues. For example, if the DDL or DML operations fail to be performed after the data synchronization task is started, DTS immediately retries the operations within the time range. Valid values: 1 to 1440. Unit: minutes. Default value: 10. We recommend that you set the parameter to a value greater than 10. If the failed operations are successfully performed within the specified time range, DTS resumes the data synchronization task. Otherwise, the data synchronization task fails.
ImportantThe value of the The wait time before a retry when other issues occur in the source and destination databases parameter must be smaller than the value of the Retry Time for Failed Connection parameter.
Enable Throttling for Full Data Migration
During full data migration, DTS uses the read and write resources of the source and destination databases. This may increase the loads of the database servers. You can configure the Queries per second (QPS) to the source database, RPS of Full Data Migration, and BPS of Full Data Migration parameters for full data synchronization tasks to reduce the pressure on the destination database.
NoteThis parameter can be configured only if Full Data Synchronization is selected as Synchronization Types.
Enable Throttling for Incremental Data Synchronization
You can configure the RPS of Incremental Data Migration and BPS of Incremental Data Migration parameters for incremental data synchronization tasks to reduce the pressure on the destination database.
Shard Configuration
The number of primary shards and the number of replica shards for each primary shard. You can specify the numbers based on the default shard configuration of the destination Elasticsearch cluster.
String Index
The method used to index strings that are synchronized to the destination Elasticsearch cluster. Valid values:
analyzed: The strings are analyzed before indexing. You must select a specific analyzer. For more information about the analyzer types, see Built-in analyzer reference.
not analyzed: The strings are indexed with the original values.
no: The strings are not indexed.
Time Zone
The time zone of the date of the DATETIME or TIMESTAMP type to be synchronized to the Elasticsearch cluster.
NoteIf the date and time data types in the destination cluster do not need a time zone, you must specify the document type for the date and time data types.
DOCID
No configuration is required. The default value of this parameter is the primary key of the table in the destination Elasticsearch cluster. If the table does not have a primary key, the value of this parameter is the ID column that is automatically generated by Elasticsearch.
Configure ETL
Specifies whether to configure the extract, transform, and load (ETL) feature. For more information, see What is ETL?. Valid values:- Yes: configures the ETL feature. You can enter data processing statements in the code editor. For more information, see Configure ETL in a data migration or data synchronization task.
- No: does not configure the ETL feature.
In the lower part of the page, click Next: Configure Database and Table Fields. On the page that appears, set the _routing policy and _id value of the tables that you want to synchronize to the destination Elasticsearch cluster.
Type
Description
Set _routing.
Specifies whether to store a document on a specific shard of the destination Elasticsearch cluster. For more information, see _routing.
If you select Yes, you can specify custom columns for routing.
If you select No, the _id value is used for routing.
NoteIf the version of the destination Elasticsearch cluster is 7.x, you must select No.No
_routing Column
The column that is used for routing.
NoteThis parameter is required only if the Set _routing parameter is set to Yes.
Value of _id
The column that is used to store the IDs of documents.
Click Next: Save Task Settings and Precheck in the lower part of the page.
You can move the pointer over Next: Save Task Settings and Precheck and click Preview OpenAPI parameters to view the parameter settings of the API operation that is called to configure the instance.
NoteBefore you can start the data synchronization task, DTS performs a precheck. You can start the data synchronization task only after the task passes the precheck.
If the task fails to pass the precheck, click View Details next to each failed item. After you troubleshoot the issues based on the causes, run a precheck again.
If an alert is triggered for an item during the precheck:
If an alert item cannot be ignored, click View Details next to the failed item and troubleshoot the issues. Then, run a precheck again.
If an alert item can be ignored, click Confirm Alert Details. In the View Details dialog box, click Ignore. In the message that appears, click OK. Then, click Precheck Again to run a precheck again. If you ignore the alert item, data inconsistency may occur, and your business may be exposed to potential risks.
Wait until the success rate becomes 100%. Then, click Next: Purchase Instance.
On the Purchase Instance page, configure the Billing Method and Instance Class parameters for the data synchronization instance. The following table describes the parameters.
Section
Parameter
Description
New Instance Class
Billing Method
Subscription: You pay for the instance when you create an instance. The subscription billing method is more cost-effective than the pay-as-you-go billing method for long-term use.
Pay-as-you-go: A pay-as-you-go instance is charged on an hourly basis. The pay-as-you-go billing method is suitable for short-term use. If you no longer require a pay-as-you-go instance, you can release the pay-as-you-go instance to reduce costs.
Resource Group
The resource group on which the instance is run. Default value: default resource group. For more information, see What is Resource Management?.
Instance Class
DTS provides various synchronization specifications that provide different performance. The synchronization speed varies based on the synchronization specifications that you select. You can select a synchronization specification based on your business scenario. For more information, see Specifications of data synchronization instances.
Subscription Duration
If you select the subscription billing method, set the subscription duration and the number of instances that you want to create. The subscription duration can be one to nine months, one year, two years, three years, or five years.
NoteThis parameter is available only if you select the Subscription billing method.
Read and select the check box to agree to the Data Transmission Service (Pay-as-you-go) Service Terms.
Click Buy and Start to start the data synchronization task. You can view the progress of the task in the task list.