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

sysbench report "Information schema is out of date",TiKV log show "Region is unavailable" #26544

Closed
Lily2025 opened this issue Jul 26, 2021 · 4 comments
Assignees
Labels
affects-5.1 This bug affects 5.1.x versions. severity/major sig/transaction SIG:Transaction type/bug The issue is confirmed as a bug.

Comments

@Lily2025
Copy link

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

  1. run sysbench work load
    tableNum = 128
    tableSize = 10000000000
    threads=128

run_type = 'oltp_write_only'
2. About after 20 minutes,report some error

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

The workload is running normally

3. What did you see instead (Required)

About after 20 minutes,report some error
4dea1c99-a6e1-4e13-b3c4-1c4e4ef443da

4. What is your TiDB version? (Required)

| Release Version: v5.1.1
Edition: Community
Git Commit Hash: fb0eaf7
Git Branch: heads/refs/tags/v5.1.1
UTC Build Time: 2021-07-23 13:18:59
GoVersion: go1.16.4
Race Enabled: false
TiKV Min Version: v3.0.0-60965b006877ca7234adaced7890d7b029ed1306
Check Table Before Drop: false |

@Lily2025 Lily2025 added the type/bug The issue is confirmed as a bug. label Jul 26, 2021
@sticnarf
Copy link
Contributor

I encountered the same problem before when I was testing high write pressure on TiDB. The root cause is probably tikv/tikv#10169. The issue makes the region containing the schema data cannot serve read requests, so TiDB cannot update its schema in time.

This issue is expected to be solved after tikv/tikv#10249 remove the write stall from TiKV.

@cfzjywxk
Copy link
Contributor

@sticnarf
Should we close this issue by now?

@sticnarf
Copy link
Contributor

@sticnarf
Should we close this issue by now?

I think so. After write stall is removed, this issue should not happen.

@Lily2025 If you encounter the same problem after TiKV 5.2, free free to reopen this issue.

@github-actions
Copy link

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

@jebter jebter added affects-5.1 This bug affects 5.1.x versions. and removed needs-more-info labels Aug 31, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
affects-5.1 This bug affects 5.1.x versions. severity/major sig/transaction SIG:Transaction type/bug The issue is confirmed as a bug.
Projects
None yet
Development

No branches or pull requests

4 participants