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

tiflash storage RU may exceed the RU_PER_SEC #8362

Closed
guo-shaoge opened this issue Nov 13, 2023 · 3 comments · Fixed by #8369
Closed

tiflash storage RU may exceed the RU_PER_SEC #8362

guo-shaoge opened this issue Nov 13, 2023 · 3 comments · Fixed by #8369

Comments

@guo-shaoge
Copy link
Contributor

guo-shaoge commented Nov 13, 2023

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

  1. setup a cluster of v7.5 or higher(for my cluster , there is 4 tiflash)
  2. import ch benchmark (1000 warehouses)
  3. create a user and its corresponding rg whose UR_PER_SEC is 30K
  4. run tpch bench with two clients, each use 1 ap thread(cmd is : tiup bench ch run -t 1 -T 1 -D tpcc -P 29989 -U u2 -p 1234)

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

RU not exceeds 30K

3. What did you see instead (Required)

we can see total RU usage exceed 30K
image

4. What is your TiFlash version? (Required)

v7.5.0

@guo-shaoge
Copy link
Contributor Author

root cause: because storage currently use read thread pool, so storage RU is not controled, need to refine it.

@guo-shaoge
Copy link
Contributor Author

@JinheLin is working on this

@guo-shaoge
Copy link
Contributor Author

This critical because without this fix, tiflash resource control will report wrong RU usage. So changed to critical.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants