phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Cody Marcel (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PHOENIX-2528) Pherf JVM doesn't exit due to un-closed ThreadPool
Date Tue, 15 Dec 2015 20:37:46 GMT

    [ https://issues.apache.org/jira/browse/PHOENIX-2528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15058750#comment-15058750
] 

Cody Marcel commented on PHOENIX-2528:
--------------------------------------

Thanks for the patch Josh. +1 to removing the system.exit(). Instead of adding a shutdown
method, can you just add the pool shutdown to the complete() method provided by the interface?

> Pherf JVM doesn't exit due to un-closed ThreadPool
> --------------------------------------------------
>
>                 Key: PHOENIX-2528
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-2528
>             Project: Phoenix
>          Issue Type: Bug
>            Reporter: Josh Elser
>            Assignee: Josh Elser
>             Fix For: 4.7.0
>
>         Attachments: PHOENIX-2528.patch
>
>
> In trying to use the pherf tool in "cluster" mode, the invocation of {{Pherf}} never
exited. I had removed a {{System.exit(0)}} already because it was suppressing an Exception.
> The JVM never exited because there were a number of threads (8) still running and not
marked as daemon. After a while, I finally tracked down these threads to {{WriteWorkload}}
which didn't bother to close the pool.
> I believe the System.exit was forcing the JVM to exit instead of letting it exit naturally.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message