apache/incubator-seata

rpcMergeMessageSend_TMROLE_1、rpcMergeMessageSend_RMROLE_1的cpu使用率过高

Open

#6,041 创建于 2023年11月17日

在 GitHub 查看
 (4 评论) (0 反应) (0 负责人)Java (25,960 star) (8,878 fork)batch import
good first issuetask: help-wantedtype: optimize

描述

  • I have searched the issues of this repository and believe that this is not a duplicate.

Ⅰ. Issue Description

seata版本：1.4.2 服务配置：-Xms512m -Xmx1024m -XX:MaxNewSize=128m 因一直收到线上某服务cpu使用率过高的告警，就先nacos进行下线，准备重启大法，发现还是一直告警。然后arthas排查，最后发现无流量情况下， rpcMergeMessageSend_TMROLE_1、rpcMergeMessageSend_RMROLE_1这2线程的cpu使用率过高

Ⅱ. Describe what happened

"rpcMergeMessageSend_TMROLE_1" Id=31 cpuUsage=31% TIMED_WAITING on java.lang.Object@1c0c220d at java.lang.Object.wait(Native Method) - waiting on java.lang.Object@1c0c220d at io.seata.core.rpc.netty.AbstractRpcRemotingClient$MergedSendRunnable.run(AbstractRpcRemotingClient.java:301) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30) at java.lang.Thread.run(Thread.java:748)

Number of locked synchronizers = 1
- java.util.concurrent.ThreadPoolExecutor$Worker@4998e74b

"rpcMergeMessageSend_RMROLE_1" Id=34 cpuUsage=30% TIMED_WAITING on java.lang.Object@25b70c1e at java.lang.Object.wait(Native Method) - waiting on java.lang.Object@25b70c1e at io.seata.core.rpc.netty.AbstractRpcRemotingClient$MergedSendRunnable.run(AbstractRpcRemotingClient.java:301) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30) at java.lang.Thread.run(Thread.java:748)

Number of locked synchronizers = 1
- java.util.concurrent.ThreadPoolExecutor$Worker@2b08772d
-

If there is an exception, please attach the exception trace:

Just paste your stack trace here!

Ⅲ. Describe what you expected to happen

Ⅳ. How to reproduce it (as minimally and precisely as possible)

  1. xxx
  2. xxx
  3. xxx

Minimal yet complete reproducer code (or URL to code):

Ⅴ. Anything else we need to know?

Ⅵ. Environment:

  • JDK version(e.g. java -version):1.8
  • Seata client/server version: 1.0.0/1.4.2
  • Database version:
  • OS(e.g. uname -a):
  • Others:

贡献者指南

技术栈
java
领域
backendperformance
议题类型
performance
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
4
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
over 1 week
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
active
清晰度议题是否清楚说明期望改动、验收标准和下一步。
needs investigation
前置要求
Java threadingSeata internalsCPU profilingRPC merging
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
15
研究方向
Investigate the MergedSendRunnable in AbstractRpcRemotingClient.java line 301. The threads are in TIMED WAITING but consuming high CPU, suggesting a possible busy wait or spurious wake up loop. Check the wait condition and notify mechanism. Also examine the merge message logic in the same file to see if there's an infinite loop. Consider using profiling tools like async profiler to identify hotspots. Look at recent commits related to this file for potential fixes.
rpcMergeMessageSend_TMROLE_1、rpcMergeMessageSend_RMROLE_1的cpu使用率过高 · apache/incubator-seata#6041 | Good First Issue