1. Classified the pipeline task status into task-level status and table-level status.
Added task-level statuses: Starting, Pausing, and To Be Retried.
Added table-level statuses: Pending Initialization, Initializing, Pending Full Synchronization, Pending Incremental Synchronization, Dirty Data Processing in Progress, and Aborted.
2. Displayed a prompt when a table was aborted.
On the detail page of a single pipeline task:
Supported redirection to the page of its real-time capture task.
Displayed log parsing latency when the source end was a MySQL, Oracle, or SQL Server database.
Displayed the latest message read/write time.
Added a table-level status Paused, and updated the status Pending Initialization to To Be Started.
Added a task-level status Resetting.
After configuring data pipeline tasks, IT personnel need to monitor the task running status.
When you click a task in the task list, you can view its running status, such as Starting, Running, Aborted, and so on. You can also check the table status, such as To Be Started, Aborted, Incremental Synchronization in Progress, and so on, as shown in the following figure.
The marked content is explained in the following table.
You can view the task running status, such as Aborted, Running, and Starting.
You can view the latest startup time of the task.
For tasks in the Starting status, a progress indicator is added to show the currently executing startup items and their results.
Example: You can click the icon to view the check items. This function has been added since FineDataLink V4.2.1.1, as shown in the following figure.
The information shown in this area is described as follows:
1. You can view the source data type.
2. You can view the latest read time of the source data.
3. You can view the log parsing latency (added since V4.2.6.3).
This information is only displayed when the data source type is MySQL, Oracle, or SQL Server. For MySQL or Oracle databases, the value is calculated as follows:Latest log time on the source database - Current parsed message time
For SQL Server databases, the calculation logic is:
First, calculate single-table latency: Latest message time in the source table's corresponding CDC table - Current parsed message time
Then, take the minimum value among all single-table latencies to obtain the overall log parsing latency.
4. When you hover over the data connection to the source database, you can click the arrow button to be redirected to Real-Time Capture Task (added since V4.2.6.3), as shown in the following figure.
You can view the target data type.
You can view the latest time of data writes to the target.
You can start/pause the task.
You can click Edit to enter the editing page of the task.
The following table describes the processing logic and subsequent state transitions when a pipeline task is in a given status.
(New in V4.2.1.1)
Pausing
To Be Retried
Resetting
(New in V4.2.11.3)
The following table describes the processing logic and subsequent state transitions when a table in the pipeline task is in a given status.
To Be Started
This is the initial status of a table.
If the task start is not completed, and the table has not started initialization, the table status remains in To Be Started.
During resynchronization, the table status starts from To Be Started.
Initializing
Pending Full Synchronization
Pending Incremental Synchronization
The full synchronization is completed. The table waits to proceed to the incremental synchronization process.
Incremental synchronization starts only when all tables in the task have entered this status.
Dirty Data Processing in Progress
For tasks with the Retry After Failure function enabled, if a table is in the Incremental Synchronization in Progress status and the dirty data volume reaches the threshold, dirty data retry will be automatically triggered according to the configuration, and the table status will change to Dirty Data Processing in Progress.
After processing, if the volume of dirty data falls below the threshold, the table status will return to Incremental Synchronization in Progress. If the dirty data still reaches or exceeds the threshold after the specified number of retries, the table status will change to Aborted.
Aborted
The system does not synchronize data in tables in this status.
You can handle dirty data and resume table synchronization through operations such as resynchronizing the table, retrying dirty data, and ignoring dirty data.
If all tables in the task are in the Aborted status, the task status will become Aborted.
Stopped
滑鼠選中內容，快速回饋問題
滑鼠選中存在疑惑的內容，即可快速回饋問題，我們將會跟進處理。
不再提示
10s後關閉
Submitted successfully
Network busy