What does "invalid tiflash table replica sync progress key" mean?

Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.

Original topic: invalid tiflash table replica sync progress key,tiflash表副本同步进度键无效。这指的什么?

| username: ddmasato

【TiDB Usage Environment】Production Environment
【TiDB Version】5.4
【Reproduction Path】Spark tasks continuously generate related logs
【Encountered Problem: Problem Phenomenon and Impact】
【Resource Configuration】Go to TiDB Dashboard - Cluster Info - Hosts and take a screenshot of this page

【Attachments: Screenshots/Logs/Monitoring】

By querying the relevant source code, it comes from the “Get TiFlash Table Replication Synchronization Progress” stage

What does this represent?

| username: Billmay表妹 | Original post link

There may be the following situations:

  1. TiFlash replica synchronization progress key error: Data synchronization between TiDB and TiFlash is conducted through the progress key. If the progress key is invalid, it may be due to configuration errors or other reasons. You can check the configuration files of TiDB and TiFlash to ensure that the progress key settings are correct.
  2. Network or connection issues: Data synchronization between TiDB and TiFlash requires network communication. If the network connection is unstable or there are other connection issues, it may cause the synchronization progress key to be invalid. You can check if the network connection is normal and ensure that there are no issues with the connection between TiDB and TiFlash.
  3. Incompatible TiDB or TiFlash versions: Data synchronization between TiDB and TiFlash requires version compatibility. If the versions of TiDB or TiFlash are incompatible, it may cause the synchronization progress key to be invalid. You can check if the versions of TiDB and TiFlash match and ensure their compatibility.
| username: Jellybean | Original post link

It looks like an INFO level log. It might be that the Region key range of the data changed during the internal raft learner data replication in TiFlash (such as merge, split, etc.). If the occurrence is not frequent, it should not be a problem.

You can check the INFORMATION_SCHEMA.TIFLASH_REPLICA system table to confirm whether the synchronization progress of the TiFlash replica is normal.

| username: dba远航 | Original post link

Learned.

| username: ddmasato | Original post link

Thank you~ Currently, because there is only one TiFlash node, the synchronized data tables are very few, only 6, and their status is normal. According to the log feedback, it appears roughly every ten seconds. Is this considered frequent?

| username: Jellybean | Original post link

This amount is not considered frequent, just keep an eye on it.

| username: 有猫万事足 | Original post link

tispark’s bug. Upgrade the tispark version.

| username: ddmasato | Original post link

Bro, awesome!

| username: system | Original post link

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.