Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

faq: update the description of "Information schema is out of date" (#18946) #18958

Merged
merged 2 commits into from
Sep 20, 2024
Merged

faq: update the description of "Information schema is out of date" (#18946) #18958

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
70679ed
faq: update the description of "Information schema is out of date"
Oreoxmt Sep 19, 2024
eff583f
Apply suggestions from code review
Oreoxmt Sep 20, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion faq/sql-faq.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -298,7 +298,7 @@

### 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 as follows:

Check failure on line 301 in faq/sql-faq.md

View workflow job for this annotation

GitHub Actions / vale 

[vale] reported by reviewdog 🐶
[PingCAP.Units] Put a nonbreaking space between the number and the unit in '45s'.

Raw Output:
{"message": "[PingCAP.Units] Put a nonbreaking space between the number and the unit in '45s'.", "location": {"path": "faq/sql-faq.md", "range": {"start": {"line": 301, "column": 93}}}, "severity": "ERROR"}

- 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.
Expand Down
Loading