-
Notifications
You must be signed in to change notification settings - Fork 5.9k
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
Resource control quota maybe exceed in some scenarios #47421
Labels
affects-7.1
This bug affects the 7.1.x(LTS) versions.
affects-7.5
This bug affects the 7.5.x(LTS) versions.
affects-8.1
This bug affects the 8.1.x(LTS) versions.
affects-8.2
component/pd
severity/major
type/bug
The issue is confirmed as a bug.
Comments
it can't go too far beyond the specified RU rate, so I think that's reasonable. Let me lower the bug level first. |
It meets the expectations in the current implementation. |
5 tasks
This was referenced Jul 4, 2024
5 tasks
3 tasks
This was referenced Jul 25, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
affects-7.1
This bug affects the 7.1.x(LTS) versions.
affects-7.5
This bug affects the 7.5.x(LTS) versions.
affects-8.1
This bug affects the 8.1.x(LTS) versions.
affects-8.2
component/pd
severity/major
type/bug
The issue is confirmed as a bug.
Bug Report
Please answer these questions before submitting your issue. Thanks!
1. Minimal reproduce step (Required)
some workloads run together and set ru limit
![img_v2_4f1b3c06-27da-40fb-b1f9-94cbd950dafg](https://private-user-images.githubusercontent.com/7677963/273378326-1f15cea2-219f-4995-9b31-653512101dac.jpg?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzkyNTU3NzcsIm5iZiI6MTczOTI1NTQ3NywicGF0aCI6Ii83Njc3OTYzLzI3MzM3ODMyNi0xZjE1Y2VhMi0yMTlmLTQ5OTUtOWIzMS02NTM1MTIxMDFkYWMuanBnP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI1MDIxMSUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNTAyMTFUMDYzMTE3WiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9OTcwNDM4YzQxOGE1MDNjYjMwYjlkMzYwNTk0ZGU4OGRkY2MzMzk2Yjg0M2UyMDVmYmVlNDZmYzgyOTYxOTVhNCZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QifQ.Q_uRBzzSGwFul1mpwqto5DBRikwhNPUuqG7H8l-9v2c)
tpcc 80k limit and the workload fluctuates around 80k, with a maximum reaching 88k.
It is somewhat related to the current implementation. When a request comes in, the RU consumption is added first, rather than after wait. In the case of tpcc, the write RU consumption is relatively high with request. It indicates a small peak, exceeding 10%.
2. What did you expect to see? (Required)
resource usage is under ru limit
3. What did you see instead (Required)
4. What is your TiDB version? (Required)
master
The text was updated successfully, but these errors were encountered: