Setting a Repair Mode for Abnormal Tables

Scenarios

When handling incremental DDL, HTAP synchronization tasks may encounter errors, causing data inconsistencies between the OLAP and OLTP sides. These issues appear as abnormal tables. TaurusDB provides automatic repair for abnormal tables. It periodically checks for abnormal 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 TaurusDB console.
2. Click in the upper left corner and select a region and project.
3. On the Instances page, locate a TaurusDB instance and click its name to access the Basic Information page.
4. In the navigation pane, choose HTAP Analysis.
5. Click the name of an HTAP instance to access the Basic Information page.
6. In the navigation pane, choose Data Synchronization. On the displayed page, click Create Synchronization Task.
7. On the displayed page, set error_table_fix_mode in the Parameter Settings area.
   Figure 1 Setting a repair mode
   

   Table 1 Repair modes

   Repair Mode	Description
   automatic (default)	Abnormal tables will be automatically repaired.
   manual	Abnormal tables will be manually repaired.
   schedule	Abnormal tables will be repaired in the maintenance window (02:00–06:00). The maintenance window cannot be changed.