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

Concurrent flush lead to CPU waste #5409

Closed
breezewish opened this issue Jul 19, 2022 · 0 comments · Fixed by #5410
Closed

Concurrent flush lead to CPU waste #5409

breezewish opened this issue Jul 19, 2022 · 0 comments · Fixed by #5410
Labels
affects-5.4 This bug affects the 5.4.x(LTS) versions. affects-6.1 This bug affects the 6.1.x(LTS) versions. component/storage severity/minor type/bug The issue is confirmed as a bug.

Comments

@breezewish
Copy link
Member

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

Perform two flush over the same segment concurrently. One could be triggered in background and another could be triggered via write.

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

One flush wait for another.

3. What did you see instead (Required)

CPU is 100% during one flush waiting for another.

4. What is your TiFlash version? (Required)

master

@breezewish breezewish added the type/bug The issue is confirmed as a bug. label Jul 19, 2022
@breezewish breezewish added affects-6.1 This bug affects the 6.1.x(LTS) versions. affects-6.2 affects-5.4 This bug affects the 5.4.x(LTS) versions. severity/minor labels Jul 19, 2022
ti-chi-bot pushed a commit that referenced this issue Jul 27, 2022
ti-chi-bot added a commit that referenced this issue Aug 22, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
affects-5.4 This bug affects the 5.4.x(LTS) versions. affects-6.1 This bug affects the 6.1.x(LTS) versions. component/storage severity/minor type/bug The issue is confirmed as a bug.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants