hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Purtell (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (HBASE-5025) Two threads named pool-1-thread-1 and pool-2-thread-1 remains after the shutdown of a cluster
Date Sat, 11 Apr 2015 01:01:13 GMT

     [ https://issues.apache.org/jira/browse/HBASE-5025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Andrew Purtell resolved HBASE-5025.
-----------------------------------
    Resolution: Not A Problem

> Two threads named pool-1-thread-1 and pool-2-thread-1 remains after the shutdown of a
cluster
> ---------------------------------------------------------------------------------------------
>
>                 Key: HBASE-5025
>                 URL: https://issues.apache.org/jira/browse/HBASE-5025
>             Project: HBase
>          Issue Type: Bug
>          Components: IPC/RPC, test
>    Affects Versions: 0.94.0
>            Reporter: Nicolas Liochon
>            Priority: Minor
>
> There are two issues with these threads:
>  - there should have a better name.  pool-x-thread-y is the default name given by java.util.concurrent.Executors
>  - these threads should not survive to a minicluster shutdown
> They are created by org.apache.hadoop.ipc.Server$Listener (with version 0.20.205.0; the
code was different before), so the first issue is a hadoop common one. It's unclear for the
second one, it could be hadoop-common as well. 
> Constructor for org.apache.hadoop.ipc.Server$Listener:
> {noformat}
>     public Listener() throws IOException {
>       //...
>       readPool = Executors.newFixedThreadPool(readThreads);  // Lack a ThreadFactory
to set the names
>       //...
>     }
> {noformat}
> Server#stop shutdowns the thread pool.



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

Mime
View raw message