-
Notifications
You must be signed in to change notification settings - Fork 726
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
remove legacy tokenSlot of resource group bucket #7346
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.
report/customer
Customers have encountered this bug.
severity/minor
type/bug
The issue is confirmed as a bug.
Comments
nolouch
added
type/bug
The issue is confirmed as a bug.
severity/major
and removed
type/enhancement
The issue or PR belongs to an enhancement.
labels
Nov 10, 2023
CabinfeverB
removed
type/bug
The issue is confirmed as a bug.
severity/major
may-affects-5.3
may-affects-5.4
may-affects-6.1
may-affects-6.5
may-affects-7.1
may-affects-7.5
labels
Nov 10, 2023
nolouch
added
type/bug
The issue is confirmed as a bug.
severity/major
affects-7.1
This bug affects the 7.1.x(LTS) versions.
affects-7.5
This bug affects the 7.5.x(LTS) versions.
and removed
needs-type
Indicates an issue requires a type label.
labels
Nov 10, 2023
ti-chi-bot
bot
added
may-affects-5.3
may-affects-5.4
may-affects-6.1
may-affects-6.5
labels
Nov 10, 2023
CabinfeverB
added
needs-type
Indicates an issue requires a type label.
type/bug
The issue is confirmed as a bug.
and removed
may-affects-6.1
may-affects-6.5
affects-7.1
This bug affects the 7.1.x(LTS) versions.
affects-7.5
This bug affects the 7.5.x(LTS) versions.
labels
Nov 10, 2023
CabinfeverB
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.
labels
Nov 10, 2023
IMO, the weight we use is a quadratic function, if the load gap between clients is too large, it will still give too much to the low-load client. 0 is a limiting case. |
ti-chi-bot bot
pushed a commit
that referenced
this issue
Nov 10, 2023
close #7346 Signed-off-by: guo-shaoge <[email protected]>
after #7344, change it to minor |
ti-chi-bot bot
pushed a commit
that referenced
this issue
Nov 10, 2023
close #7346 Signed-off-by: guo-shaoge <[email protected]> Co-authored-by: guo-shaoge <[email protected]>
ti-chi-bot bot
added a commit
that referenced
this issue
Dec 11, 2023
close #7346 Signed-off-by: guo-shaoge <[email protected]> Co-authored-by: guo-shaoge <[email protected]> Co-authored-by: ti-chi-bot[bot] <108142056+ti-chi-bot[bot]@users.noreply.github.com>
18 tasks
17 tasks
github-project-automation
bot
moved this from Need Triage
to Closed
in Questions and Bug Reports
Nov 21, 2024
/report customer |
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.
report/customer
Customers have encountered this bug.
severity/minor
type/bug
The issue is confirmed as a bug.
Enhancement Task
Normally when node step out gracefully(got SIGTERM etc), it will send last acquire grpc, so PD will cleanup its slot token.
But when node crash unexpctedly or got SIGKILL(which cannot be handled), it will have no chance to send last acquire grpc, so its corresponding slot token will leave here forever, which makes fillrate/burstLimit be less.
The text was updated successfully, but these errors were encountered: