[
https://issues.apache.org/jira/browse/HBASE-15770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15274904#comment-15274904
]
Hadoop QA commented on HBASE-15770:
-----------------------------------
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:red}-1{color} | {color:red} patch {color} | {color:red} 0m 5s {color}
| {color:red} HBASE-15770 does not apply to master. Rebase required? Wrong
Branch? See https://yetus.apache.org/documentation/0.2.1/precommit-patchnames
for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12802753/HBASE-15770-v1.patch |
| JIRA Issue | HBASE-15770 |
| Console output |
https://builds.apache.org/job/PreCommit-HBASE-Build/1806/console |
| Powered by | Apache Yetus 0.2.1 http://yetus.apache.org |
This message was automatically generated.
> 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)
