-
Notifications
You must be signed in to change notification settings - Fork 439
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
[BUG]System Guard flow control | CPU thredshold| 系统自适应流控|以CPU作为阈值场景下的取值范围问题 #539
Comments
我使用的gosutil是最新的版本
|
sunyucheng
changed the title
System Guard flow control | CPU thredshold| 系统自适应流控|以CPU作为阈值场景下的取值范围问题
[FAQ]System Guard flow control | CPU thredshold| 系统自适应流控|以CPU作为阈值场景下的取值范围问题
Jun 28, 2023
sunyucheng
changed the title
[FAQ]System Guard flow control | CPU thredshold| 系统自适应流控|以CPU作为阈值场景下的取值范围问题
[DISCUSSION]System Guard flow control | CPU thredshold| 系统自适应流控|以CPU作为阈值场景下的取值范围问题
Jun 28, 2023
Hi @sczyh30 ,可以给我一些意见么 |
sunyucheng
changed the title
[DISCUSSION]System Guard flow control | CPU thredshold| 系统自适应流控|以CPU作为阈值场景下的取值范围问题
[BUG]System Guard flow control | CPU thredshold| 系统自适应流控|以CPU作为阈值场景下的取值范围问题
Jun 29, 2023
this could be a bug, are you interested in fixing it |
Certainly |
Hi @binbin0325, I have already mentioned PR #540 |
May I ask why this fix has not passed? Is it not ready to be repaired? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
背景:
我在测试使用CPU作为阈值的系统自适应流控方案。
问题:
1、在 func IsValidSystemRule(rule *Rule) error中校验的 cpu取值范围为0.0~1.0。但是在实际测试中发现func getProcessCpuStat() (float64, error)函数的实际返回值大小为0.0~100.0。导致在注册规则时因阈值非法
invalid CPU usage, valid range is [0.0, 1.0]
而失败。该处是否应该修改一下cpu的合法性校验范围。
The text was updated successfully, but these errors were encountered: