funky-eyes commented on issue #7497: URL: https://github.com/apache/incubator-seata/issues/7497#issuecomment-3034749014
该问题在2.4版本后得到改善，但是并没有完全解决，因为2.4版本修复了客户端只有1个io线程的问题。只是缓解了这个问题发生的概率。我认为因为将exceptionCaught中调用releaseChannel的方法改为使用reconnect线程池去运行异步运行，因为reconnect线程池只有1个线程数，线程安全，也不会再阻塞netty的io线程。 This issue has been improved in version 2.4, but it hasn't been completely resolved, because version 2.4 only fixed the problem of the client having only 1 I/O thread. It merely reduced the probability of this issue occurring. I think we should change the releaseChannel method call in exceptionCaught to run asynchronously using the reconnect thread pool, because the reconnect thread pool has only 1 thread, which is thread-safe and won't block Netty's I/O threads anymore. -- 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: notifications-unsubscr...@seata.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: notifications-unsubscr...@seata.apache.org For additional commands, e-mail: notifications-h...@seata.apache.org
