LambertZhaglog
LambertZhaglog
Following the advice of @Wei-Huang (see pr https://github.com/kubernetes/community/pull/6478) **Which issue(s) this PR fixes**: 1. remove the out-of-dated file scheduler_algorithm.md 2. replaced the link entry in devel/README.md to "Scheduler Configuration" (with...
**Describe the bug** 参见[这里](https://hpbn.co/http2/#streams-messages-and-frames) 对connection, stream, message 的定义。在一个TCP connection上,Kindling不能正确处理下面两种类型的通信场景 case1: 两个流的response message 逆序 case2: client发起的流包裹 server 发起的流 图示如下  case1: Client 连续向Server发送两个请求request1 和 request2,Server先响应了response2,后响应response1。 按照当前 [Network.ConsumeEvent](https://github.com/KindlingProject/kindling/blob/main/collector/pkg/component/analyzer/network/network_analyzer.go#L156)的处理逻辑:request2 报文会被merge到request1的尾部(即request2被隐藏),response1 会被丢弃,request1 和response2会被错误的配对在一起,进行 [NetworkAnalyzer.distributeTraceMetric](https://github.com/KindlingProject/kindling/blob/mian/collector/pkg/component/analyzer/network/network_analyzer.go#L313)分析...