All Products
Search
Document Center

DataWorks:Serverless synchronization task configuration

Last Updated:Jun 20, 2026

This topic describes the features of serverless synchronization tasks in Data Integration and explains how to configure them.

Limits

  • Supported regions: China (Hangzhou), China (Shanghai), China (Beijing), China (Zhangjiakou), China (Shenzhen), China (Hong Kong), UK (London), US (Silicon Valley), US (Virginia), Japan (Tokyo), Germany (Frankfurt), Malaysia (Kuala Lumpur).

  • Supported synchronization types:

    • MySQL to Hologres: Real-time synchronization of an entire database

    • MySQL to MaxCompute: Real-time synchronization of an entire database

    • MySQL to StarRocks: Real-time synchronization of an entire database

  • This feature supports only data sources that belong to your Alibaba Cloud account and are in the current region.

Notes

  • Serverless synchronization tasks do not use resource groups, which allows you to focus on the task itself.

  • You do not need to configure network connectivity for serverless synchronization tasks. However, the VPC CIDR blocks associated with the source and destination data sources must not overlap.

  • Serverless synchronization tasks are pay-as-you-go. When a task starts, an Order ID is automatically generated. You can use this Order ID to view detailed billing information in the Alibaba Cloud order system. For more information about billing, see Performance metrics of DataWorks serverless resource groups.

  • A serverless task is billed on a pay-as-you-go basis only when it is running. Billing stops when the task is not running. If a task is no longer needed, you can delete it. This operation is irreversible. Deleting a task also releases its associated order.

Note

You can view the fees incurred by a serverless task by using its billing Order ID in Orders.

Procedure

Step 1: Create a serverless task

  1. Log on to the DataWorks console. In the target region, click Data Integration > Data Integration in the left-side navigation pane. Select a workspace from the drop-down list and click Go to Data Integration.

  2. In the left-side navigation pane, click Serverless Synchronization Task.

  3. In the Serverless Synchronization Task area, select a Source and a Destination, and then click Create Serverless Synchronization Task.

Step 2: Configure basic information

  • To use an existing data source, click Use Existing Data Source and select one from the list. The information about the data source is automatically retrieved.

  • You do not need to add the Data Source and Destination data sources in Data Integration beforehand. You can directly configure the detailed information for the Data Source or Destination on this page.

  • After configuring the source and destination information, click Test. For Alibaba Cloud RDS and Hologres instances, the connectivity test automatically passes if no IP address whitelist is configured. If an IP address whitelist is configured, you must add the required IP addresses to the whitelist. For a list of the IP addresses, see Network Connectivity and Whitelist Configuration.

Step 3: Task configuration

Follow the on-screen instructions to configure the synchronization settings based on your specific task type.

Step 4: Complete the configuration

After configuring the preceding information, click Complete.

The first time you Complete, a Configuration Check is automatically performed. Note that this Configuration Check does not block Complete and is only a pre-check.

Start the task

  • Starting the task triggers another Configuration Check. Note that this Configuration Check is mandatory. If the check fails, the task cannot start.

  • The items in a configuration check vary depending on the synchronization task.

  • When starting a task for the first time, the system checks if the user has the required permissions. The permissions are the same as those required for purchasing pay-as-you-go serverless general-purpose resource groups. Only users with AliyunBSSOrderAccess and AliyunDataWorksFullAccess permissions can start the task.

Task details

Click an entry in the Name/ID or Execution Overview column to go to the task details page.

  • Basic information: includes the task's data source information, Order ID, and synchronization plan.

  • Execution status: shows the execution status of each step in the synchronization task. You can also view the runtime log, failover details, and resource utilization.

  • Detailed information: includes details about schema migration, full data initialization, and real-time synchronization.

Task modification

  1. In the Actions column for the target task, click Edit to go to the task configuration page.

  2. You can add, delete, or modify the tables to be synchronized, and then click Complete.

  3. In the Actions column, click Apply Updates.

    • When you Apply Updates, a pre-check is automatically performed. If the check fails, the Apply Updates is blocked.

    • The check for Apply Updates has fewer items than the check for the initial start. Because the resources are already initialized, the resource preparation phase is skipped when you Apply Updates, unlike during the initial start.

Appendix

Task order details

Unlike other types of synchronization tasks, serverless synchronization tasks do not use resource groups. They are settled based on task-specific orders and are pay-as-you-go.

Note

A serverless task is billed on a pay-as-you-go basis only when it is running. Billing stops when the task is not running. If a task is no longer needed, you can delete it. This operation is irreversible. Deleting a task also releases its associated order.

You can query for an order in the following ways:

  1. Click an entry in the Name/ID or Execution Overview column to go to the task details page.

  2. In the Basic Information area, obtain the Order ID.

  3. Go to the Alibaba Cloud Orders page and search for the order by using the Order ID.

Advanced configuration

Synchronization source and rules

By default, the task synchronizes data to a destination schema and tables with the same names as the source. The task automatically creates the schema or tables in the destination if they do not exist. You can also use the Customize Mapping Rules for Destination Schema Names and Customize Mapping Rules for Destination Table Names options to define the final names of the schema or tables in the destination. This allows you to replace a prefix in the source names with a different prefix for the destination names.

Destination table

You can define the properties of the destination table. For example, you can specify whether to write data to an existing table or a new table, add a Field, specify whether to write data to a partitioned table, and set the Partition Field name, Storage Mode, and Value assignment.

Note

In this step, after clicking the Apply and Refresh Mapping button, the source and destination tables are mapped based on the configured rules.

Write rules

If your source data involves frequent DDL or DML operations, you can configure a DDL or DML message processing policy to ensure data integrity at the destination. For more information, see DDL Message Processing Rules and DML Message Processing Policies.