You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, it looks like the threads are not cleaned after the processor stops.
I created 5 different Nakadi clients, each with maxRetryAttempts set to 2 and started the processes. They are made to fail by having another client(another process) use the same subscription. I saw that the onStop() method was called 5 times after processor was shutdown.
I can see that there are still even after 15mins of processor stopping,
RxComputationThreadPool * 8 threads running ( looks like this is constant and is not increasing by increasing the clients) -
RxSchedulerPurge * 1 ,
RxCachedWorkerPoolEvictor * 1 these threads are still running.
However
OkHttp ConnectionPool * 5 - Each per client
1 Okio Watchdog, 1 OkHttpConnection Pool are getting cleaned up after approx 5mins.
Hi, it looks like the threads are not cleaned after the processor stops.
I created 5 different Nakadi clients, each with maxRetryAttempts set to 2 and started the processes. They are made to fail by having another client(another process) use the same subscription. I saw that the onStop() method was called 5 times after processor was shutdown.
When I printed the thread dump after r
I can see that there are still even after 15mins of processor stopping,
RxComputationThreadPool * 8 threads running ( looks like this is constant and is not increasing by increasing the clients) -
RxSchedulerPurge * 1 ,
RxCachedWorkerPoolEvictor * 1 these threads are still running.
However
OkHttp ConnectionPool * 5 - Each per client
1 Okio Watchdog, 1 OkHttpConnection Pool are getting cleaned up after approx 5mins.
Total 10 threads are not cleaned up.
Here is the output.
Could you confirm if this is a bug or am I missing something here?
Thanks.
The text was updated successfully, but these errors were encountered: