Skip to content

Commit

Permalink
Update ticdc/ticdc-open-api-v2.md
Browse files Browse the repository at this point in the history
  • Loading branch information
qiancai authored and ti-chi-bot committed Feb 21, 2024
1 parent 89623aa commit dfb97e1
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion ticdc/ticdc-open-api-v2.md
Original file line number Diff line number Diff line change
Expand Up @@ -866,7 +866,7 @@ This example shows the response of an ongoing replication task. By checking both
}
```

This API enables you to query the synchronization status even when the upstream cluster encounters disasters. In certain situations, you might not be able to directly determine whether the current data replication task of TiCDC is completed or not. In such cases, you can request this API, and then check both the `info` field in the result and the current status of the upstream cluster to determine the specific status.
This API enables you to query the synchronization status even when the upstream cluster encounters disasters. In certain situations, you might not be able to directly determine whether the current data replication task of TiCDC is completed or not. In such cases, you can request this API, and then check both the `info` field in the response and the current status of the upstream cluster to determine the specific status.

In this example, `sink_checkpoint_ts` is behind `now_ts` in time, either because TiCDC is still catching up with data replication, or because the PD or TiKV has failed. If this is due to TiCDC still catching up with data replication, it means that the replication task is not completed yet. If this is due to a PD or TiKV failure, it means that the replication task is completed. Therefore, you need to check the `info` field to assist in determining the cluster status.

Expand Down

0 comments on commit dfb97e1

Please sign in to comment.