Overview
Ops monitoring for real-time synchronization tasks covers the complete task lifecycle from publishing, starting, and running to stopping. This document describes how to view the task list, Ops details page, run logs, link details, and DDL change records, as well as common Ops operations such as starting, restarting, stopping, modifying the owner, and modifying alarms.
Prerequisites
The current account has the corresponding permissions on the task in the target Workspace: View / Edit / Run / Manage (for details, see Members and Permission Management). Task Status
Status | Description | Available Operations (Primary Operation + More) |
Unpublished | Task created but not published | Publish, Edit, Permission, Delete |
Pending start | Task published but not started. | Start, Edit, Permission, Delete (After edits are saved, the primary operation changes to Publish) |
In progress | Intermediate state of start, stop, or restart | - |
Running | Stable running state after successful startup | Stop, Force Stop, Restart, Edit, Permission |
Running (with updates) | A running task is edited and published again. | Restart (Primary Operation), Stop, Force Stop, Edit, Permission |
Running (abnormal) | The number of restarts is greater than 1 within 10 minutes; the status is followed by the exception reason. | Stop, Force Stop, Restart, Edit, Permission |
Stopped | Stop operation completed. | Start, Edit, Permission, Delete |
Failed | Startup failed (for example, startup timed out) or running failed (for example, the maximum number of restarts was reached); the status is followed by the exception reason. | Start, Edit, Permission, Delete |
Operation Steps
Step 1: Opening the Task List
2. Switch to the target region and Workspace at the top.
3. Go to Data Integration > Task Management > Real-Time Synchronization.
The task list displays the task name/ID, task type, status, data source, owner, creator, and update time. It supports fuzzy search by task name/ID and filtering by source type, data source connection, target Catalog, and compute resource.
Step 2: Publishing the Task
1. Select an Unpublished task and click Publish.
2. In the publish dialog, select:
Publish only: After publishing, the task enters the Pending Start state.
Publish and start: After publishing, the task directly enters the startup process (for details, see Step 3). Step 3: Starting the Task
Starting involves three steps: detection → selecting a startup policy → viewing progress.
1. Task Startup Detection: The platform checks the completeness of the task configuration.
2. Select a startup policy: Different policies are available based on the current task state. For details, see Startup and Restart Policies. 3. View Progress and Results: You can click View Run Details to go to the task Ops details page, or click Close to return to the list.
Start and Restart Policies
Current status | Optional startup policy | Remarks |
Pending start | Start immediately and sync from the default position; start immediately and sync from a specified position; start immediately and sync from a specified point in time | Only MySQL / Tencent Cloud MySQL / TDSQL-C MySQL data sources support specified positions and specified points in time. |
Running / Running (with updates) / Running (abnormal) | Continue running and resume from the last position while retaining the job state; restart and resume from a specified point in time / a specified position; restart and start from the default position while discarding the job state. | "Continue running" applies to scenarios where the state does not need to be discarded after configuration changes. |
Stopped | Same as the above four options | - |
Failed | Resume from the Checkpoint where the last run failed; restart and start from the default position. | - |
Step 4: Viewing Ops Details
Click the task name to go to the Ops details page:
Task Name Navigation Area: Return to the list, copy the task name, and add to favorites.
Task Actions Area: Start, stop, edit, delete, and permissions (Delete and Permissions are collapsed into "More").
Task Basic Information Area: Task name, ID, type, data source, compute resource, run identity, start time, creator, and creation time. Data source and compute resource support click-through navigation.
Configuration Details: Displays the task configuration of the latest published version.
Step 5: Common Ops Operations
Operation | Entries | Action |
Starting | Start in the list / operation area on the details page | |
Stop. | Stop in the list / operation area on the details page | Graceful stop |
Force stop | Force stop in the list / operation area on the details page | Skip graceful process and terminate immediately. |
Restart | Restart in the list / operation area on the details page | Equivalent to stop + start |
Editing an alarm policy | Edit in the list / operation area on the details page | Go to the task editing page. |
Permission | Permissions in the list / More on the details page | |
Modify owner. | More > Modify owner in the list | |
Alarm | More > Alarm in the list | Directly modify alarm channels / alarm types / thresholds without republishing. |
Deleting an alarm policy | More > Delete in the list | Delete after secondary confirmation; running tasks must be stopped first. |
Permission Management
Task permissions are controlled based on ACL entities. You can assign permissions such as Manage / Run / Edit / View to members. For details on permission semantics, see Members and Permission Management. Changing the Owner
The owner is the actual account that runs the task. For a running task, after the owner is changed, the task must be restarted for the change to take effect. Before the restart, an info icon appears after the Owner column in the list, indicating that the owner has been changed and the change will take effect only after a restart. When you change the owner from the Edit Task page, you must publish the task before starting it.
Execution result
Task Execution Status and Progress
Real-time tasks display progress in three stages: Environment Preparation → Full Sync → Incremental Sync.
Phase | Description | Progress display |
Preparing the Environment | Task initialization (resource readiness, connection establishment, and more) | One-time phase |
Full synchronization | Sync all existing data from the source table to the target table. | Progress percentage + completed / total tables |
Incremental synchronization | Continuously sync real-time changes from the source. | Current latency (such as "2-second latency"), and "Stopped" when it is stopped |
Trace Details
Display the sync status of each table in a list: source database, source Schema (if any) / source table, target Catalog / target Schema / target table, target connection method, table creation DDL / rows read, rows written, rows updated, rows deleted, and status.
Action | Description |
Filter search | Source/target database, Schema, table, target connection method, and status can all be filtered. |
Sort | Read quantity/write quantity support sorting. |
Status | Normal / Abnormal (The specific reason is displayed when an exception occurs during running). |
Jump | |
Table creation DDL | When the target connection method is "Auto table creation", the complete table creation DDL is displayed; when it is "Use existing table", - is displayed. |
DDL Change Records
This feature is supported only when the source type is MySQL / Tencent Cloud MySQL / TDSQL-C MySQL. For other source types, "DDL change records are not supported for the current link" is displayed.
Record fields: source database, source Schema (if any) / source table, target Catalog / target Schema / target table, change time, change policy, source table DDL statement, target table DDL statement, and change status.
Change Status | Conditions for Occurrence |
Successful | The change policy is "automatic change" and the execution is successful. |
Failed | The change policy is "automatic change" but the execution fails. You can click the info icon at the end of the row to view the failure reason, and the task ignores this change by default. |
Ignored. | The change policy is "ignore". |
Run Logs
Capability | Description |
Historical logs | Historical logs can be viewed in any state, including after the system is stopped. |
Quick diagnosis | Text matching + keyword highlighting allows you to quickly locate matching content. |
Automatic refresh | Disabled by default. To view the latest logs, click Refresh manually. |
Allows you to query logs. | Supports keyword search and filtering by log level and time. |
Data Reconciliation
Verification Result
After completing the Ops operations, you can confirm in the following ways:
1. The task list status has been changed to the target status, for example, to Running after the task is started, or to Stopped after the task is stopped.
2. The progress updates for the environment preparation, full sync, and incremental sync stages on the Task Details page are as expected.
3. The number of rows read and written for each table in the Link Details list continues to grow during the incremental sync stage.
4. There are no abnormal events in the Run Logs.
FAQs
Q: Why Does a Task Remain in the "In Progress" State?
A: "Operating" is an intermediate state of start, stop, and restart. It usually transitions to the next state automatically within minutes. If it remains in this state for a long time:
1. Check whether the run logs contain any error information.
3. If you confirm that the system is stuck, contact technical support for assistance.
Q: How Do I Troubleshoot the "Running (Abnormal)" State?
A: Running (Abnormal) is usually triggered when the number of restarts within 10 minutes is > 1. Troubleshoot in the following order:
1. The abnormal reason prompt after the status.
2. The most recent error stack in the run logs.
3. Filter abnormal tables in Link Details and view the cause.
4. Check whether there are any failed changes in the DDL change records. When the change policy is "Automatic Change" and the execution fails, the task ignores the failure by default, but this may cause abnormal data writes later.
5. Check the alarm notifications to confirm whether the Failover restart quantity threshold has been exceeded.
Q: Why Does a Task Still Run with the Old Account After the Owner Is Changed?
A: After the owner is changed, the task must be restarted for the change to take effect. Click Restart at an appropriate time. Otherwise, the task continues to run as the original owner. If the change was made from the Edit Task page, you must publish the task before starting it.
Q: Can a Task Be Recovered After Deletion?
A: Deletion is a terminal operation. Perform the steps in the following order with caution: Stop → Confirm no dependencies → Delete. A running task cannot be deleted directly. You must stop it before deleting it.
Q: Can I Start Multiple Tasks at Once?
A: The current task list does not provide a batch start entry. Each task must be started individually.
References