Ignite node thread dump after applying quick and dirty solution - just added *ThreadPoolExecutor.allowCoreThreadTimeOut(true)* to base thread pool:
"srvc-deploy-#20%null%" "exchange-worker-#19%null%" "ttl-cleanup-worker-#18%null%" "grid-time-coordinator-#17%null%" "grid-time-server-reader-#16%null%" "disco-event-worker-#15%null%" "tcp-disco-ip-finder-cleaner-#5%null%" "tcp-disco-srvr-#4%null%" "tcp-disco-msg-worker-#3%null%" "grid-data-loader-flusher-#14%null%" "tcp-comm-worker-#1%null%" "grid-nio-worker-3-#12%null%" "grid-nio-worker-2-#11%null%" "grid-nio-worker-1-#10%null%" "grid-nio-worker-0-#9%null%" "nio-acceptor-#8%null%" "grid-timeout-worker-#7%null%" Looks pretty nice to me. Now need to finalize and benchmark it. On Thu, Sep 29, 2016 at 2:05 PM, Vladimir Ozerov <[email protected]> wrote: > Created ticket: https://issues.apache.org/jira/browse/IGNITE-4001 > > On Thu, Sep 29, 2016 at 12:25 PM, Alexey Kuznetsov < > [email protected]> wrote: > >> Just as idea - >> >> if we implement stop thread after some idle time, may be it make sense to >> add a line to log about this? >> >> -- >> Alexey Kuznetsov >> > >
