Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Mon, 9 May 2016 19:31:12 +0000 (UTC)
From: "Elliott Clark (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12965128.1462404960000.145403.1462822272923@Atlassian.JIRA>
In-Reply-To: <JIRA.12965128.1462404960000@Atlassian.JIRA>
References: <JIRA.12965128.1462404960000@Atlassian.JIRA> <JIRA.12965128.1462404960088@arcas>
Subject: [jira] [Updated] (HBASE-15770) Stop using wangle's global executor
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Mon, 09 May 2016 19:31:14 -0000


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

Elliott Clark updated HBASE-15770:
----------------------------------
    Resolution: Fixed
        Status: Resolved  (was: Patch Available)

> Stop using wangle's global executor
> -----------------------------------
>
>                 Key: HBASE-15770
>                 URL: https://issues.apache.org/jira/browse/HBASE-15770
>             Project: HBase
>          Issue Type: Sub-task
>            Reporter: Elliott Clark
>            Assignee: Elliott Clark
>            Priority: Blocker
>         Attachments: HBASE-15770-v1.patch, HBASE-15770.patch
>
>
> In order to ensure that all things are closed correctly, we need to call IOThreadPool#close. Doing that on the singleton is pretty bad manners. So we should just use our own IOThreadPool and not use the global one at all.
> This will involve making the client have the threads.
> Passing the threads to connection pool, connection factory, etc.
> Calling close on the threads when cleaning up the client.


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