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.

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

br: Error: [ddl:1069]Too many keys specified; max 64 keys allowed #48664

Closed
qybf opened this issue Nov 17, 2023 · 3 comments
Closed

br: Error: [ddl:1069]Too many keys specified; max 64 keys allowed #48664

qybf opened this issue Nov 17, 2023 · 3 comments
Labels
component/br This issue is related to BR of TiDB. type/bug The issue is confirmed as a bug.

Comments

@qybf
Copy link

qybf commented Nov 17, 2023

My TiDB version is v6.5.3. When I try to restore a full backup from S3 to a new TiDB database using BR, I encounter an error. The error message is as follows:

"Error: [ddl:1069]Too many keys specified; max 64 keys allowed."

I have already configured index-limit = 512, but I still encounter the error. How can I verify if the index-limit value in my database is indeed set to 512?

@qybf qybf added the type/bug The issue is confirmed as a bug. label Nov 17, 2023
@jebter jebter added the component/br This issue is related to BR of TiDB. label Nov 20, 2023
@BornChanger
Copy link
Contributor

@qybf , the problem is already fixed in version 6.5.4 via issue #45793.

@BornChanger
Copy link
Contributor

/close

@ti-chi-bot ti-chi-bot bot closed this as completed Mar 27, 2024
Copy link

ti-chi-bot bot commented Mar 27, 2024

@BornChanger: Closing this issue.

In response to this:

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component/br This issue is related to BR of TiDB. type/bug The issue is confirmed as a bug.
Projects
None yet
Development

No branches or pull requests

3 participants