Setting a Repair Mode for Abnormal Tables

Scenarios

An exception may occur when an HTAP synchronization task processes incremental DDL statements. As a result, AP data may be inconsistent with TP data. In this case, an abnormal table is displayed. TaurusDB provides automatic repair for abnormal tables. It periodically checks abnormal data tables and creates temporary tasks to repair them based on the repair mode.

Constraints

• A synchronization task can have only one repair task. A maximum of five repair tasks can run on an instance at the same time. If there are too many repair tasks, they will be executed in subsequent periods.
• If a repair task fails multiple times, the repair task automatically stops.
• Abnormal tables caused by RENAME DDL statements on a database need to be manually repaired.

Setting a Repair Mode for Abnormal Tables

1. Log in to the management console.
2. Click in the upper left corner and select a region and project.
3. Click in the upper left corner of the page and choose Databases > TaurusDB.
4. On the Instances page, locate a TaurusDB instance and click its name to access the Basic Information page.
5. In the navigation pane, choose HTAP Analysis.
6. Click the name of an HTAP instance to access the Basic Information page.
7. In the navigation pane, choose Data Synchronization. Click Create Synchronization Task. On the displayed page, set error_table_fix_mode.

   The following three repair modes are supported. The default value is automatic.

   • manual: Abnormal tables will be manually repaired.
   • automatic: Abnormal tables will be automatically repaired.
   • schedule: Abnormal tables will be repaired in the maintenance time window (02:00–06:00).
   Figure 1 Setting a repair mode