QiuYucheng2003 commented on issue #9983: URL: https://github.com/apache/rocketmq/issues/9983#issuecomment-3717072321
Thanks for the clarification. I understand that RocketMQ currently does not use CallerRunsPolicy by default. However, the main motivation behind this issue is defensive programming. If users customize the thread pool and accidentally configure it with CallerRunsPolicy, it will block the Netty IO thread, leading to severe availability issues (e.g., heartbeat timeout). I suggest adding a check during the processor registration to explicitly forbid or warn against this policy, just to prevent potential misuse. -- 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]
