Troubleshoot a TiFlash Cluster

This section describes some commonly encountered issues when using TiFlash, the reasons, and the solutions.

TiFlash fails to start

The issue might occur due to different reasons. It is recommended that you troubleshoot it following the steps below:

Check whether your system is RedHat Enterprise Linux 8.
RedHat Enterprise Linux 8 does not have the libnsl.so system library. You can manually install it via the following command:
```
dnf install libnsl
```
Check your system's ulimit parameter setting.
```
ulimit -n 1000000
```
Use the PD Control tool to check whether there is any TiFlash instance that failed to go offline on the node (same IP and Port) and force the instance(s) to go offline. For detailed steps, refer to Scale in a TiFlash cluster.

If the above methods cannot resolve your issue, save the TiFlash log files and get support from PingCAP or the community.

TiFlash replica is always unavailable

This is because TiFlash is in an abnormal state caused by configuration errors or environment issues. Take the following steps to identify the faulty component:

Check whether PD enables the Placement Rules feature:
```
echo 'config show replication' | /path/to/pd-ctl -u http://${pd-ip}:${pd-port}
```
- If true is returned, go to the next step.
- If false is returned, enable the Placement Rules feature and go to the next step.
Check whether the TiFlash process is working correctly by viewing UpTime on the TiFlash-Summary monitoring panel.
Check whether the TiFlash proxy status is normal through pd-ctl.
```
echo "store" | /path/to/pd-ctl -u http://${pd-ip}:${pd-port}
```
The TiFlash proxy's store.labels includes information such as {"key": "engine", "value": "tiflash"}. You can check this information to confirm a TiFlash proxy.
Check whether pd buddy can correctly print the logs (the log path is the value of log in the [flash.flash_cluster] configuration item; the default log path is under the tmp directory configured in the TiFlash configuration file).
Check whether the number of configured replicas is less than or equal to the number of TiKV nodes in the cluster. If not, PD cannot replicate data to TiFlash:
```
echo 'config placement-rules show' | /path/to/pd-ctl -u http://${pd-ip}:${pd-port}
```
Reconfirm the value of default: count.
Note
- When Placement Rules are enabled and multiple rules exist, the previously configured max-replicas, location-labels, and isolation-level no longer take effect. To adjust the replica policy, use the interface related to Placement Rules.
- When Placement Rules are enabled and only one default rule exists, TiDB will automatically update this default rule when max-replicas, location-labels, or isolation-level configurations are changed.
Check whether the remaining disk space of the machine (where store of the TiFlash node is) is sufficient. By default, when the remaining disk space is less than 20% of the store capacity (which is controlled by the low-space-ratio parameter), PD cannot schedule data to this TiFlash node.

Some queries return the `Region Unavailable` error

If the load pressure on TiFlash is too heavy and it causes that TiFlash data replication falls behind, some queries might return the Region Unavailable error.

In this case, you can balance the load pressure by adding more TiFlash nodes.

Data file corruption

Take the following steps to handle the data file corruption:

Refer to Take a TiFlash node down to take the corresponding TiFlash node down.
Delete the related data of the TiFlash node.
Redeploy the TiFlash node in the cluster.

TiFlash analysis is slow

If a statement contains operators or functions not supported in the MPP mode, TiDB does not select the MPP mode. Therefore, the analysis of the statement is slow. In this case, you can execute the EXPLAIN statement to check for operators or functions not supported in the MPP mode.

create table t(a datetime);
alter table t set tiflash replica 1;
insert into t values('2022-01-13');
set @@session.tidb_enforce_mpp=1;
explain select count(*) from t where subtime(a, '12:00:00') > '2022-01-01' group by a;
show warnings;

In this example, the warning message shows that TiDB does not select the MPP mode because TiDB 5.4 and earlier versions do not support the subtime function.

+---------+------+-----------------------------------------------------------------------------+
> | Level   | Code | Message                                                                     |
+---------+------+-----------------------------------------------------------------------------+
| Warning | 1105 | Scalar function 'subtime'(signature: SubDatetimeAndString, return type: datetime) is not supported to push down to tiflash now.       |
+---------+------+-----------------------------------------------------------------------------+

Data is not replicated to TiFlash

After deploying a TiFlash node and starting replication (by performing the ALTER operation), no data is replicated to it. In this case, you can identify and address the problem by following the steps below:

Check whether the replication is successful by running the ALTER table <tbl_name> set tiflash replica <num> command and check the output.
- If there is output, go to the next step.
- If there is no output, run the SELECT * FROM information_schema.tiflash_replica command to check whether TiFlash replicas have been created. If not, run the ALTER table ${tbl_name} set tiflash replica ${num} command again, check whether other statements (for example, add index) have been executed, or check whether DDL executions are successful.
Check whether TiFlash Region replication runs correctly.
Check whether there is any change in progress:
- If yes, TiFlash replication runs correctly.
- If no, TiFlash replication is abnormal. In tidb.log, search the log saying Tiflash replica is not available. Check whether progress of the corresponding table is updated. If not, check the tiflash log for further information. For example, search lag_region_info in tiflash log to find out which Region lags behind.
Check whether the Placement Rules function has been enabled by using pd-ctl:
```
echo 'config show replication' | /path/to/pd-ctl -u http://<pd-ip>:<pd-port>
```
- If true is returned, go to the next step.
- If false is returned, enable the Placement Rules feature and go to the next step.
Check whether the max-replicas configuration is correct:
- If the value of max-replicas does not exceed the number of TiKV nodes in the cluster, go to the next step.
- If the value of max-replicas is greater than the number of TiKV nodes in the cluster, the PD does not replicate data to the TiFlash node. To address this issue, change max-replicas to an integer fewer than or equal to the number of TiKV nodes in the cluster.
Note
max-replicas is defaulted to 3. In production environments, the value is usually fewer than the number of TiKV nodes. In test environments, the value can be 1.
```
    curl -X POST -d '{
        "group_id": "pd",
        "id": "default",
        "start_key": "",
        "end_key": "",
        "role": "voter",
        "count": 3,
        "location_labels": [
        "host"
        ]
    }' <http://172.16.x.xxx:2379/pd/api/v1/config/rule>
```
Check whether TiDB has created any placement rule for tables.
Search the logs of TiDB DDL Owner and check whether TiDB has notified PD to add placement rules. For non-partitioned tables, search ConfigureTiFlashPDForTable. For partitioned tables, search ConfigureTiFlashPDForPartitions.
- If the keyword is found, go to the next step.
- If not, collect logs of the corresponding component for troubleshooting.
Check whether PD has configured any placement rule for tables.
Run the curl http://<pd-ip>:<pd-port>/pd/api/v1/config/rules/group/tiflash command to view all TiFlash placement rules on the current PD. If a rule with the ID being table-<table_id>-r is found, the PD has configured a placement rule successfully.
Check whether the PD schedules properly.
Search the pd.log file for the table-<table_id>-r keyword and scheduling behaviors like add operator.
- If the keyword is found, the PD schedules properly.
- If not, the PD does not schedule properly.

Data replication gets stuck

If data replication on TiFlash starts normally but then all or some data fails to be replicated after a period of time, you can confirm or resolve the issue by performing the following steps:

Check the disk space.
Check whether the disk space ratio is higher than the value of low-space-ratio (defaulted to 0.8. When the space usage of a node exceeds 80%, the PD stops migrating data to this node to avoid exhaustion of disk space).
- If the disk usage ratio is greater than or equal to the value of low-space-ratio, the disk space is insufficient. To relieve the disk space, remove unnecessary files, such as space_placeholder_file (if necessary, set reserve-space to 0MB after removing the file) under the ${data}/flash/ folder.
- If the disk usage ratio is less than the value of low-space-ratio, the disk space is sufficient. Go to the next step.
Check whether there is any down peer (a down peer might cause the replication to get stuck).
Run the pd-ctl region check-down-peer command to check whether there is any down peer. If any, run the pd-ctl operator add remove-peer <region-id> <tiflash-store-id> command to remove it.

Data replication is slow

The causes may vary. You can address the problem by performing the following steps.

Increase store limit to accelerate replication.
Adjust the load on TiFlash.
Excessively high load on TiFlash can also result in slow replication. You can check the load of TiFlash indicators on the TiFlash-Summary panel on Grafana:
- Applying snapshots Count: TiFlash-summary > raft > Applying snapshots Count
- Snapshot Predecode Duration: TiFlash-summary > raft > Snapshot Predecode Duration
- Snapshot Flush Duration: TiFlash-summary > raft > Snapshot Flush Duration
- Write Stall Duration: TiFlash-summary > Storage Write Stall > Write Stall Duration
- generate snapshot CPU: TiFlash-Proxy-Details > Thread CPU > Region task worker pre-handle/generate snapshot CPU
Based on your service priorities, adjust the load accordingly to achieve optimal performance.