iamssx opened a new issue, #6226:
URL: https://github.com/apache/rocketmq/issues/6226

   use the default config to start up a rocketmq cluster,when it run for a 
month or so, there will be a jvm crash because of oom. we try to modify the 
linux memory arguments , and that is not worked. and we get the jvm dump and 
thread stack. now we found that a lot of FlowMonitor  thread  wating, and it 
keep increase.we suspect the amount of flowmonitor thread is the reason of jvm 
crash.  
   
   please read the thread analysis and jvm crash, and tell us the true reason 
why it crash, and the way to fix it, thanks!
   
    environment: 
   rocketmq 5.0.0
   linux redhat7.9, 48Core/755GB MEM  
   
   /usr/local/jdk/bin/java -server -Xms8g -Xmx8g -XX:+UseG1GC 
-XX:G1HeapRegionSize=16m -XX:G1ReservePercent=25 
-XX:InitiatingHeapOccupancyPercent=30 -XX:SoftRefLRUPolicyMSPerMB=0 -verbose:gc 
-Xloggc:/dev/shm/rmq_srv_gc_%p_%t.log -XX:+PrintGCDetails 
-XX:+PrintGCDateStamps -XX:+PrintGCApplicationStoppedTime 
-XX:+PrintAdaptiveSizePolicy -XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=5 
-XX:GCLogFileSize=30m -XX:-OmitStackTraceInFastThrow -XX:+AlwaysPreTouch 
-XX:MaxDirectMemorySize=15g -XX:-UseLargePages -XX:-UseBiasedLocking 
-Drocketmq.client.logUseSlf4j=true -cp 
.:/data/rocketmq-all-5.0.0-bin-release//bin/../conf:/data/rocketmq-all-5.0.0-bin-release//bin/../lib/*:
 -Djdk.tls.rejectClientInitiatedRenegotiation=true 
org.apacherocketmq.broker.BrokerStartup -c 
/data/rocketmq/conf/broker-c.properties
   
   the jvm crash info:
   
![image](https://user-images.githubusercontent.com/10175456/222363197-0915c51b-d6e6-40ea-81b5-3f945fcf3e64.png)
   
   thread dump:
   
https://fastthread.io/my-thread-report.jsp?p=c2hhcmVkLzIwMjMvMDMvMi90aHJlYWQudHh0LS03LTE0LTU2&;


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to