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

Transaction conflict on internal SQL, "mysql.table_cache_meta" table #32386

Closed
tiancaiamao opened this issue Feb 15, 2022 · 0 comments · Fixed by #32387
Closed

Transaction conflict on internal SQL, "mysql.table_cache_meta" table #32386

tiancaiamao opened this issue Feb 15, 2022 · 0 comments · Fixed by #32387
Labels
feature/developing the related feature is in development severity/minor sig/sql-infra SIG: SQL Infra type/bug The issue is confirmed as a bug.

Comments

@tiancaiamao
Copy link
Contributor

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

core bank testing using table caching

2. What did you expect to see? (Required)

Everything goes well

3. What did you see instead (Required)

Found some warning log:

can't retry for update statement 'select lock_type, lease, oldReadLease from mysql.table_cache_meta where tid ...'

4. What is your TiDB version? (Required)

master eabd78c

@tiancaiamao tiancaiamao added type/bug The issue is confirmed as a bug. severity/minor feature/developing the related feature is in development labels Feb 15, 2022
@tiancaiamao tiancaiamao changed the title Transaction conflict on internal SQL, table "mysql.table_cache_meta" Transaction conflict on internal SQL, "mysql.table_cache_meta" table Feb 15, 2022
@ChenPeng2013 ChenPeng2013 added the sig/sql-infra SIG: SQL Infra label Feb 16, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature/developing the related feature is in development severity/minor sig/sql-infra SIG: SQL Infra type/bug The issue is confirmed as a bug.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants