On 9/9/17 12:16 AM, William Allen Simpson wrote:
On 9/8/17 9:44 AM, Daniel Gryniewicz wrote:
On 09/08/2017 09:07 AM, William Allen Simpson wrote:
On 9/7/17 10:47 PM, Malahal Naineni wrote:
Last time I tried, I got the same. A thread was waiting in epoll_wait() with 29
second timeout that, it
On 9/8/17 9:44 AM, Daniel Gryniewicz wrote:
On 09/08/2017 09:07 AM, William Allen Simpson wrote:
On 9/7/17 10:47 PM, Malahal Naineni wrote:
Last time I tried, I got the same. A thread was waiting in epoll_wait() with 29
second timeout that, it was working after such a timeout.
I have seen th
On 09/08/2017 09:07 AM, William Allen Simpson wrote:
On 9/7/17 10:47 PM, Malahal Naineni wrote:
Last time I tried, I got the same. A thread was waiting
in epoll_wait() with 29 second timeout that, it was working after such
a timeout.
I have seen the same, after I sped up the work pool shutdo
On 9/7/17 10:47 PM, Malahal Naineni wrote:
Last time I tried, I got the same. A thread was waiting inĀ epoll_wait() with 29
second timeout that, it was working after such a timeout.
I have seen the same, after I sped up the work pool shutdown. The work
pool shutdown will nanosleep 1 second int
Last time I tried, I got the same. A thread was waiting in epoll_wait()
with 29 second timeout that, it was working after such a timeout.
On Fri, Sep 8, 2017 at 3:46 AM, Frank Filz wrote:
> I wanted to see what is up with shutdown lately...
>
> Running under gdb, I hit a long pause, but shutdown
I wanted to see what is up with shutdown lately...
Running under gdb, I hit a long pause, but shutdown is completing for me,
during that pause, these are the active threads:
(gdb) thread apply all bt
Thread 276 (Thread 0x7fff6b2fb700 (LWP 5364)):
#0 0x7638027d in nanosleep () from /lib6