Fork me on GitHub
#core-async
<
2019-01-18
>
tianshu09:01:34

increasing threads.

tianshu09:01:23

I found there're a lot async-thread-macro have a Park states. is it okay? they keep increasing

tianshu09:01:19

I use the thread macro is a async block for jdbc operation and use some pipeline-blocking

alexmiller13:01:14

That doesn’t look ok

alexmiller13:01:11

What do you mean by an async block?

noisesmith18:01:45

sounds like the code inside thread is not returning, so the threads are not freed?

noisesmith18:01:54

@doglooksgood you can use the threads tab to look at the stack traces and see what all those supposedly live threads are doing - perhaps you asked them to do a blocking put on a channel that isn't being read?

hiredman18:01:51

my guess would be something similar, go blocks launching threads and not waiting for them to finish(so no feedback), and the threads are blocked on a shared resource (maybe a connection pool) so you are calling thread faster then they can complete their tasks

hiredman18:01:57

the number of live threads is less then the number of total started, which makes me guess the theads aren't blocked forever and are completing, you are just creating them faster then they complete