From 2c1d085290d9ee9a2f3f8a22026a135a0c72f254 Mon Sep 17 00:00:00 2001 From: Aolin Date: Thu, 19 Sep 2024 15:46:14 +0800 Subject: [PATCH 1/2] faq: update the description of "Information schema is out of date" --- faq/sql-faq.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/faq/sql-faq.md b/faq/sql-faq.md index d6247bced66f5..6f4dcac68a976 100644 --- a/faq/sql-faq.md +++ b/faq/sql-faq.md @@ -298,7 +298,7 @@ In the preceding causes, only Cause 1 is related to tables. Cause 1 and Cause 2 ### What are the causes of the "Information schema is out of date" error? -Before TiDB v6.5.0, when executing a DML statement, if TiDB fails to load the latest schema within a DDL lease (45s by default), the `Information schema is out of date` error might occur. Possible causes are: +When executing a DML statement, if TiDB fails to load the latest schema within a DDL lease (45s by default), the `Information schema is out of date` error might occur. Possible causes are: - The TiDB instance that executed this DML was killed, and the transaction execution corresponding to this DML statement took longer than a DDL lease. When the transaction was committed, the error occurred. - TiDB failed to connect to PD or TiKV while executing this DML statement. As a result, TiDB failed to load schema within a DDL lease or disconnected from PD due to the keepalive setting. From 4931feaae03d72ae18ef5242e32f72dd9bb6ea6d Mon Sep 17 00:00:00 2001 From: Aolin Date: Fri, 20 Sep 2024 10:31:43 +0800 Subject: [PATCH 2/2] Apply suggestions from code review Co-authored-by: Grace Cai --- faq/sql-faq.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/faq/sql-faq.md b/faq/sql-faq.md index 6f4dcac68a976..07591b11987a8 100644 --- a/faq/sql-faq.md +++ b/faq/sql-faq.md @@ -298,7 +298,7 @@ In the preceding causes, only Cause 1 is related to tables. Cause 1 and Cause 2 ### What are the causes of the "Information schema is out of date" error? -When executing a DML statement, if TiDB fails to load the latest schema within a DDL lease (45s by default), the `Information schema is out of date` error might occur. Possible causes are: +When executing a DML statement, if TiDB fails to load the latest schema within a DDL lease (45s by default), the `Information schema is out of date` error might occur. Possible causes are as follows: - The TiDB instance that executed this DML was killed, and the transaction execution corresponding to this DML statement took longer than a DDL lease. When the transaction was committed, the error occurred. - TiDB failed to connect to PD or TiKV while executing this DML statement. As a result, TiDB failed to load schema within a DDL lease or disconnected from PD due to the keepalive setting.