You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@rocketmq.apache.org by GitBox <gi...@apache.org> on 2019/11/05 09:01:31 UTC

[GitHub] [rocketmq] walterhong opened a new issue #1573: kill -9 one rocketMq broker

walterhong opened a new issue #1573: kill -9 one rocketMq broker 
URL: https://github.com/apache/rocketmq/issues/1573
 
 
   ![截图2](https://user-images.githubusercontent.com/16216936/68191734-25e9fd80-ffeb-11e9-96b5-28e1016fee85.PNG)
   after killing one rocketmq master broker, the cpu of machine which slave broker is running on become much higher than before. I use top -Hp slave broker process to find which thread cpu is the highest and use jstack to see what the thread that has the highest cpu is doing, then I get following pictures
   ![截图22](https://user-images.githubusercontent.com/16216936/68192530-68f8a080-ffec-11e9-8ec3-fed588eaf6b4.PNG)
   ![截图211](https://user-images.githubusercontent.com/16216936/68192544-6dbd5480-ffec-11e9-9c37-a4526f74f70f.PNG)
   as shown in the above pictures, asyncappender-worker-thread has the highest CPU, why does this situation happens?Hoq can I solve this question? Can I solve this question by changing parameters of rocketMq?
   
   

----------------------------------------------------------------
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.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services