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

store: unistore will hang over in some case. #24428

Closed
AilinKid opened this issue May 6, 2021 · 4 comments
Closed

store: unistore will hang over in some case. #24428

AilinKid opened this issue May 6, 2021 · 4 comments
Assignees
Labels
component/unistore severity/moderate sig/transaction SIG:Transaction type/bug The issue is confirmed as a bug.

Comments

@AilinKid
Copy link
Contributor

AilinKid commented May 6, 2021

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

https://github.com/pingcap/automated-tests/pull/658/files

start local tidb
cd ticase/column_type_change
go build
./column_type_change run -i suite.jsonnet TICASE-4941

The related goroutine
tidb_debug_20210506140729.zip

I've tested it with a real tikv, it works.

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

Test success.

3. What did you see instead (Required)

The test hangs over, do did the TiDB

4. What is your TiDB version? (Required)

master <commit 207ce34 >

@AilinKid AilinKid added type/bug The issue is confirmed as a bug. component/unistore labels May 6, 2021
@tiancaiamao
Copy link
Contributor

That's weird... from the goroutine stack, the code seems blocked in bager engine... it might happen when the runFlushMemTable goroutine exit exceptionally.

Can it reproduce?

@bb7133 bb7133 added sig/transaction SIG:Transaction and removed sig/sql-infra SIG: SQL Infra labels Aug 9, 2021
@zyguan
Copy link
Contributor

zyguan commented Dec 30, 2021

No update for a long time, feel free to reopen it if the issue still exists.

@zyguan zyguan closed this as completed Dec 30, 2021
@github-actions
Copy link

Please check whether the issue should be labeled with 'affects-x.y' or 'fixes-x.y.z', and then remove 'needs-more-info' label.

@tiancaiamao
Copy link
Contributor

The data race might be a possible reason... concurrent write breaks unistore and make it hang #26832

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component/unistore severity/moderate sig/transaction SIG:Transaction type/bug The issue is confirmed as a bug.
Projects
None yet
Development

No branches or pull requests

6 participants