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

faq: add info for schema is changed error (#6453) #6488

Merged
merged 2 commits into from
Sep 15, 2021
Merged

faq: add info for schema is changed error (#6453) #6488

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
5f48ab4
faq: add info for schema is changed error
Sep 13, 2021
c870ffb
Update faq/sql-faq.md
TomShawn Sep 15, 2021
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
Prev Previous commit
Update faq/sql-faq.md
  • Loading branch information
@TomShawn @ti-chi-bot
TomShawn authored and ti-chi-bot committed Sep 15, 2021
commit c870ffbddf497ae78a4b38c24f7ebb1277a99b8f
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 @@ -192,7 +192,7 @@ Now, there are still a few reasons for this error reporting (only the first one
+ Some tables involved in the DML operation are the same tables involved in the ongoing DDL operation.
+ The DML operation goes on for a long time. During this period, many DDL statements have been executed, which causes more than 1024 `schema` version changes. You can modify this default value by modifying the `tidb_max_delta_schema_count` variable.
+ The TiDB server that accepts the DML request is not able to load `schema information` for a long time (possibly caused by the connection failure between TiDB and PD or TiKV). During this period, many DDL statements have been executed, which causes more than 100 `schema` version changes.
+ -After TiDB restarts and before the first DDL operation is executed, the DML operation is executed and then encouters the first DDL operation (which means before the first DDL operation is executed, the transaction corresponding to the DML is started. And after the first `schema` version of the DDL is changed, the transaction corresponding to the DML is committed), this DML operation reports this error.
+ After TiDB restarts and before the first DDL operation is executed, the DML operation is executed and then encounters the first DDL operation (which means before the first DDL operation is executed, the transaction corresponding to the DML is started. And after the first `schema` version of the DDL is changed, the transaction corresponding to the DML is committed), this DML operation reports this error.

> **Note:**
>
Expand Down