trace统计reactor.netty.http.client.HttpClientFinalizer问题
Open
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 37.6k
- Forks
- 7.6k
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 4
Description
- 我已经在 issues 里搜索，没有重复的issue。
环境信息
arthas-boot.jar或者as.sh的版本： 3.6.0- Arthas 版本: 3.6.0
- 操作系统版本: k8s docker容器
- 目标进程的JVM版本: 1.8
- 执行
arthas-boot的版本: 3.6.0
重现问题的步骤
- 通过Skywalking的gateway插件发现sendRequest span耗时较长，压测的时候耗时超过1s，sendRequest对应的类是reactor.netty.http.client.HttpClientFinalizer；
- 通过trace查看reactor.netty.http.client.HttpClientFinalizer具体耗时的方法；
- 在压测过程中trace只有几条耗时几十ms的，跟skywalking的观察结果差异很大；
期望的结果
What do you expected from the above steps？
能够找到HttpClientFinalizer耗时长的原因。
实际运行的结果
无法找到耗时长的原因。
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the reported load-test scenario in the stated Arthas 3.6.0, Java 8, Kubernetes and Docker environment, then trace reactor.netty.http.client.HttpClientFinalizer while comparing the results with SkyWalking's sendRequest span. Done means identifying why Arthas reports only short calls and documenting or correcting the cause of the missing long-duration observation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- observability
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100