We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
不同服务间通过 net/metadata 来传递
net/metadata
原始重要性设置于 bm 的路由上,默认以 CRITICAL 形式存在,通过 Handler 的形式将优先级作用于每个请求中。
CRITICAL
Handler
重要性分以下几级(重要等级递减):
CRITICAL_PLUS
SHEDDABLE_PLUS
SHEDDABLE
http service 之间通过 header 形式进行传递,rpc service 之间通过 rpc metadata 形式进行传递。
在 bm 处理请求时,请求中的重要性永远优先于预设于路由上的重要性。
The text was updated successfully, but these errors were encountered:
1,如果设置了自定义重要性Handler,覆盖上游的 2,如果未设置自定义重要性Handler,继承上游的 3,如果啥都没,默认为30,即Critical,
另外TODO:
1、基于重要性结合上面的MR,来控制不同重要性接口的bbr load shedding启发值; 2、重要性后续做Per-Customer 限流,会按照服务、重要性、接口多个粒度来设置;
Sorry, something went wrong.
目前blademaster 已经支持
No branches or pull requests
不同服务间通过
net/metadata
来传递原始重要性设置于 bm 的路由上,默认以
CRITICAL
形式存在,通过Handler
的形式将优先级作用于每个请求中。重要性分以下几级(重要等级递减):
CRITICAL_PLUS
CRITICAL
SHEDDABLE_PLUS
SHEDDABLE
http service 之间通过 header 形式进行传递,rpc service 之间通过 rpc metadata 形式进行传递。
在 bm 处理请求时,请求中的重要性永远优先于预设于路由上的重要性。
The text was updated successfully, but these errors were encountered: