core.async got in a bad state?

2017-08-29 Thread Aaron Iba
My company has a production system that uses core.async extensively. We've been running it 24/7 for over a year with occasional restarts to update things and add features, and so far core.async has been working great. The other day, during a particularly high workload, the whole system got lock

Re: core.async got in a bad state?

2017-08-29 Thread Aaron Iba
ed >>> "async-dispatch-" and it looks like there are 8 blocked ones in your >>> thread dump. >>> >>> It also looks like they are all blocking on a >!!, which is a blocking >>> call. So I would look for a go block that contains a >!!