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

Count result may be wrong after a lot of insert and delete #4956

Closed
lidezhu opened this issue May 22, 2022 · 2 comments · Fixed by #4955
Closed

Count result may be wrong after a lot of insert and delete #4956

lidezhu opened this issue May 22, 2022 · 2 comments · Fixed by #4955
Assignees
@lidezhu
Labels
affects-4.0 affects-5.0 affects-5.1 affects-5.2 affects-5.3 affects-5.4 affects-6.0 affects-6.1 component/storage severity/critical type/bug The issue is confirmed as a bug.

Comments

@lidezhu
Copy link
Contributor

lidezhu commented May 22, 2022 •
edited by JaySon-Huang
Loading

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

Repeated do a lot of insert rows and delete alls.
Keep select count after after every operation.

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

Count result is right.

3. What did you see instead (Required)

Count result is wrong. The number of rows in TiFlash is larger than that in TiKV

4. What is your TiFlash version? (Required)
@lidezhu lidezhu added the type/bug The issue is confirmed as a bug. label May 22, 2022
@lidezhu lidezhu self-assigned this May 22, 2022
@lidezhu lidezhu mentioned this issue May 22, 2022
Merged
12 tasks
@JaySon-Huang
Copy link
Contributor

JaySon-Huang commented May 22, 2022 •
edited
Loading

/cc @lilinghai We need to add a test case for this kind of workload

@lilinghai
Copy link

/cc @lilinghai We need to add a test case for this kind of workload

ok. have discussed it with dezhu and I will add a test case.

@lidezhu lidezhu mentioned this issue May 23, 2022
Merged
12 tasks
This was referenced May 23, 2022
Merged
Merged
Merged
Merged
Merged
Closed
Merged
Closed
@lidezhu lidezhu mentioned this issue May 31, 2022
Merged
12 tasks
@JaySon-Huang JaySon-Huang mentioned this issue May 31, 2022
Merged
ti-chi-bot added a commit that referenced this issue Jun 1, 2022
@ti-chi-bot
flush cache before segment merge (#4955) (#4968)
aa14a01 
close #4956
ti-chi-bot added a commit that referenced this issue Jun 2, 2022
@ti-chi-bot
flush cache before segment merge (#4955) (#4965)
66b073e 
close #4956
ti-chi-bot added a commit that referenced this issue Jun 2, 2022
@ti-chi-bot
flush cache before segment merge (#4955) (#4966)
f8b2a80 
close #4956
ti-chi-bot added a commit that referenced this issue Jun 2, 2022
@ti-chi-bot
flush cache before segment merge (#4955) (#4964)
9856019 
close #4956
ti-chi-bot added a commit that referenced this issue Jun 3, 2022
@ti-chi-bot
flush cache before segment merge (#4955) (#4967)
922cca1 
close #4956
@hehechen hehechen mentioned this issue Jun 15, 2022
Closed
breezewish pushed a commit that referenced this issue Aug 29, 2022
@ti-chi-bot @breezewish
flush cache before segment merge (#4955) (#4965)
5c2a040 
close #4956
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@lidezhu lidezhu

Labels
affects-4.0 affects-5.0 affects-5.1 affects-5.2 affects-5.3 affects-5.4 affects-6.0 affects-6.1 component/storage severity/critical type/bug The issue is confirmed as a bug.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

flush cache before segment merge lidezhu/tics
4 participants
@JaySon-Huang @lilinghai @lidezhu @ti-chi-bot