When importing TPCC data, TiDB error: schemaLeaseChecker is not set for this transaction

Translated
1

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

Original topic: tpcc导入数据时TiDB刷:schemaLeaseChecker is not set for this transaction

| username: 我是咖啡哥

During the data import process, the TiDB log keeps showing: schemaLeaseChecker is not set for this transaction. It does not affect the data import, but I just want to understand what this is for?


[2023/06/19 15:07:52.502 +08:00] [WARN] [2pc.go:1802] ["schemaLeaseChecker is not set for this transaction"] [sessionID=4555687891224877163] [startTS=442278470587777029] [checkTS=442278470613991425]
2
| username: redgame | Original post link

schemaLeaseChecker is used to detect the connection status of each PD node in the TiDB cluster. If the PD cluster cannot respond to TiDB’s requests, TiDB will not be able to obtain the correct schemaLease, resulting in errors in transactions.

3
| username: 我是咖啡哥 | Original post link

It seems that this error also occurs when not importing data. It shouldn’t be a big issue. :grinning:

4
| username: system | Original post link

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