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

Unexpected cache miss for infoscheam_v2 TableByID #56295

Closed
GMHDBJD opened this issue Sep 25, 2024 · 0 comments · Fixed by #56333
Closed

Unexpected cache miss for infoscheam_v2 TableByID #56295

GMHDBJD opened this issue Sep 25, 2024 · 0 comments · Fixed by #56333
Labels
affects-8.3 component/ddl This issue is related to DDL of TiDB. feature/developing the related feature is in development severity/minor type/bug The issue is confirmed as a bug.

Comments

@GMHDBJD
Copy link
Contributor

GMHDBJD commented Sep 25, 2024

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

set cache size to 3 tables
create table tb1
create table tb2
create table tb3
create table tb4
tableByID tb1
tableByID tb2
tableByID tb3
tableByID tb4
tableByID tb2
tableByID tb3

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

last call(tableByID tb3) should be cache hit.

3. What did you see instead (Required)

last call(tableByID tb3) cache miss

4. What is your TiDB version? (Required)

master

@GMHDBJD GMHDBJD added type/bug The issue is confirmed as a bug. severity/minor feature/developing the related feature is in development affects-8.3 labels Sep 25, 2024
@jebter jebter added the component/ddl This issue is related to DDL of TiDB. label Sep 27, 2024
ti-chi-bot bot pushed a commit that referenced this issue Oct 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
affects-8.3 component/ddl This issue is related to DDL of TiDB. feature/developing the related feature is in development severity/minor type/bug The issue is confirmed as a bug.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants