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.

Sign up for GitHub

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

Jump to bottom

Exceeded resource group quota limitation if request tokens exceeded 500ms #8349

Closed
nolouch opened this issue Jul 2, 2024 · 1 comment · Fixed by #8352 or #8368
Closed

Exceeded resource group quota limitation if request tokens exceeded 500ms #8349

nolouch opened this issue Jul 2, 2024 · 1 comment · Fixed by #8352 or #8368
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 report/customer Customers have encountered this bug. severity/major type/bug The issue is confirmed as a bug.

Comments

@nolouch
Copy link
Contributor

nolouch commented Jul 2, 2024 •
edited
Loading

Bug Report

What did you do?

User use resource control.

What did you expect to see?

no error report

What did you see instead?

meet exceed resource group quota limitation, but RU usage is below the RU settings.

image

image

image

Event 1 17:40:19.765 17:40:19.765 Coming a request and finding that the local tokens are insufficient, send a notification to the thread that acquires tokens.
Event 2 17:40:19.765 ~ 17:40:20.198 17:40:20.198 The request keep retrying, but the local tokens haven't refreshed yet, continuously logging the same events as before during this retry period. After retrying 500ms timeout,the report failed error to the applications.
Event 3 17:40:20.263 ~17:40:20.265 17:40:20.263 The thread responsible for fetching Tokens received the notification and started to send requests for tokens.17:40:20.265 Obtain new tokens authorization

See the above table. Theoretically, Event 1 should immediately trigger Event 3. After Event 3 succeeds, then enough tokens are obtained during the retry period of Event 2, the request can continue. However, it is possible that since the current event-driven system is similar to a single-threaded event loop, in some cases, the processing delay of a certain message exceeds 500 ms, leading to a failure in obtaining tokens and resulting in an error.

What version of PD are you using (pd-server -V)?

7.5.2
@nolouch nolouch added the type/bug The issue is confirmed as a bug. label Jul 2, 2024
@nolouch nolouch mentioned this issue Jul 2, 2024
Merged
@nolouch nolouch added 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. and removed may-affects-5.4 may-affects-6.1 may-affects-6.5 may-affects-7.1 may-affects-7.5 may-affects-8.1 labels Jul 2, 2024
@ti-chi-bot ti-chi-bot bot closed this as completed in #8352 Jul 3, 2024
@ti-chi-bot ti-chi-bot bot closed this as completed in 6b25787 Jul 3, 2024
@nolouch nolouch mentioned this issue Jul 3, 2024
Merged
5 tasks
ti-chi-bot pushed a commit to ti-chi-bot/pd that referenced this issue Jul 4, 2024
@nolouch @ti-chi-bot
This is an automated cherry-pick of tikv#8352
a5c4b61 
close tikv#8349

Signed-off-by: ti-chi-bot <ti-community-prow-bot@tidb.io>
@ti-chi-bot ti-chi-bot mentioned this issue Jul 4, 2024
Merged
@nolouch nolouch mentioned this issue Jul 4, 2024
Merged
ti-chi-bot bot pushed a commit that referenced this issue Jul 4, 2024
@ti-chi-bot @nolouch
client/controller: record context error and add slowlog about token b…
01da6f4 
…ucket (#8344) (#8355)

close #8343, ref #8349

client/controller: record context error and add slowlog about token bucket
- record low process start time, and log it if it's too slow
- record the context error

Signed-off-by: ti-chi-bot <ti-community-prow-bot@tidb.io>
Signed-off-by: Shuning Chen <nolouch@ShuningdeMacBook-Pro.local>

Co-authored-by: ShuNing <nolouch@gmail.com>
Co-authored-by: Shuning Chen <nolouch@ShuningdeMacBook-Pro.local>
@easonn7
Copy link

easonn7 commented Jul 4, 2024

/approve

@nolouch nolouch mentioned this issue Jul 4, 2024
Merged
nolouch added a commit that referenced this issue Jul 4, 2024
@nolouch @ti-chi-bot
resource_control: allow configuration of the maximum retry time for t…
173c2e1 
…he local bucket (#8352)  (#8365)

* client/controller: record context error and add slowlog about token bucket (#8344) (#8355)

close #8343, ref #8349

client/controller: record context error and add slowlog about token bucket
- record low process start time, and log it if it's too slow
- record the context error

Signed-off-by: Shuning Chen <nolouch@ShuningdeMacBook-Pro.local>

* This is an automated cherry-pick of #8352

close #8349

Signed-off-by: nolouch <nolouch@gmail.com>
Signed-off-by: Shuning Chen <nolouch@ShuningdeMacBook-Pro.local>

---------

Signed-off-by: Shuning Chen <nolouch@ShuningdeMacBook-Pro.local>
Signed-off-by: nolouch <nolouch@gmail.com>
Co-authored-by: Ti Chi Robot <ti-community-prow-bot@tidb.io>
@nolouch nolouch mentioned this issue Jul 4, 2024
Merged
5 tasks
ti-chi-bot bot pushed a commit to pingcap/tidb that referenced this issue Jul 4, 2024
@nolouch
mod: update pd client (#54424)
9f7441a 
ref tikv/pd#8349, ref #47421
This was referenced Jul 4, 2024
Merged
Merged
Merged
Merged
ti-chi-bot bot pushed a commit to pingcap/tidb that referenced this issue Jul 5, 2024
@nolouch
[cherry-pick] mod: update the pd client (#54457)
387f691 
ref tikv/pd#8349, ref #47421
@nolouch nolouch mentioned this issue Jul 5, 2024
Merged
ti-chi-bot bot pushed a commit to pingcap/tidb that referenced this issue Jul 5, 2024
@ti-chi-bot
mod: update pd client (#54424) (#54461)
821e491 
ref tikv/pd#8349, ref #47421
This was referenced Jul 5, 2024
Merged
Merged
ti-chi-bot bot pushed a commit to pingcap/tidb that referenced this issue Jul 5, 2024
@nolouch
[cherry-pick] mod: update the pd client (#54482)
eaff0fb 
ref tikv/pd#8349, ref #47421
ti-chi-bot bot pushed a commit that referenced this issue Jul 8, 2024
@nolouch
controller: fix the low_ru request missed (#8368)
85d650b 
close #8349

controller: fix the low_ru request missed 

The problem is that `c.run.currentRequests` is shared by all groups.
If one group triggers a token request that isn't handled by the response, the other group's requests will be discarded.
Here, we do not discard the low_ru triggers.

Signed-off-by: nolouch <nolouch@gmail.com>
ti-chi-bot pushed a commit to ti-chi-bot/pd that referenced this issue Jul 8, 2024
@nolouch @ti-chi-bot
This is an automated cherry-pick of tikv#8368
d6a4c44 
close tikv#8349

Signed-off-by: ti-chi-bot <ti-community-prow-bot@tidb.io>
@ti-chi-bot ti-chi-bot mentioned this issue Jul 8, 2024
Merged
ti-chi-bot pushed a commit to ti-chi-bot/pd that referenced this issue Jul 8, 2024
@nolouch @ti-chi-bot
This is an automated cherry-pick of tikv#8368
cfeadbd 
close tikv#8349

Signed-off-by: ti-chi-bot <ti-community-prow-bot@tidb.io>
@ti-chi-bot ti-chi-bot mentioned this issue Jul 8, 2024
Merged
ti-chi-bot pushed a commit to ti-chi-bot/pd that referenced this issue Jul 8, 2024
@nolouch @ti-chi-bot
This is an automated cherry-pick of tikv#8368
e6e33c7 
close tikv#8349

Signed-off-by: ti-chi-bot <ti-community-prow-bot@tidb.io>
This was referenced Jul 8, 2024
Merged
Closed
ti-chi-bot bot pushed a commit that referenced this issue Jul 8, 2024
@ti-chi-bot @nolouch
controller: fix the low_ru request missed (#8368) (#8373)
cb8da1b 
close #8349

controller: fix the low_ru request missed 

The problem is that `c.run.currentRequests` is shared by all groups.
If one group triggers a token request that isn't handled by the response, the other group's requests will be discarded.
Here, we do not discard the low_ru triggers.

Signed-off-by: ti-chi-bot <ti-community-prow-bot@tidb.io>
Signed-off-by: nolouch <nolouch@gmail.com>

Co-authored-by: ShuNing <nolouch@gmail.com>
Co-authored-by: nolouch <nolouch@gmail.com>
ti-chi-bot bot pushed a commit that referenced this issue Jul 8, 2024
@ti-chi-bot @nolouch
controller: fix the low_ru request missed (#8368) (#8371)
05207d6 
close #8349

controller: fix the low_ru request missed 

The problem is that `c.run.currentRequests` is shared by all groups.
If one group triggers a token request that isn't handled by the response, the other group's requests will be discarded.
Here, we do not discard the low_ru triggers.

Signed-off-by: ti-chi-bot <ti-community-prow-bot@tidb.io>
Signed-off-by: nolouch <nolouch@gmail.com>

Co-authored-by: ShuNing <nolouch@gmail.com>
Co-authored-by: nolouch <nolouch@gmail.com>
ti-chi-bot bot pushed a commit that referenced this issue Jul 8, 2024
@ti-chi-bot @nolouch
controller: fix the low_ru request missed (#8368) (#8372)
19f65c5 
close #8349

controller: fix the low_ru request missed 

The problem is that `c.run.currentRequests` is shared by all groups.
If one group triggers a token request that isn't handled by the response, the other group's requests will be discarded.
Here, we do not discard the low_ru triggers.

Signed-off-by: ti-chi-bot <ti-community-prow-bot@tidb.io>
Signed-off-by: nolouch <nolouch@gmail.com>

Co-authored-by: ShuNing <nolouch@gmail.com>
Co-authored-by: nolouch <nolouch@gmail.com>
ti-chi-bot bot pushed a commit to pingcap/tidb that referenced this issue Jul 12, 2024
@ti-chi-bot
mod: update pd client (#54424) (#54459)
ed1e010 
ref tikv/pd#8349, ref #47421
ti-chi-bot bot pushed a commit to pingcap/tidb that referenced this issue Jul 12, 2024
@ti-chi-bot
mod: update pd client (#54424) (#54460)
8737e7d 
ref tikv/pd#8349, ref #47421
ti-chi-bot bot pushed a commit to pingcap/tidb that referenced this issue Jul 14, 2024
@ti-chi-bot
mod: update pd client (#54424) (#54458)
223032b 
ref tikv/pd#8349, ref #47421
@ti-chi-bot ti-chi-bot bot added the report/customer Customers have encountered this bug. label Oct 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
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 report/customer Customers have encountered this bug. severity/major type/bug The issue is confirmed as a bug.
Projects
Questions and Bug Reports
Status: Closed
Milestone
No milestone
3 participants
@nolouch @ti-chi-bot @easonn7