[
https://issues.apache.org/jira/browse/HBASE-13232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14360979#comment-14360979
]
Hudson commented on HBASE-13232:
--------------------------------
FAILURE: Integrated in HBase-TRUNK #6256 (See
[https://builds.apache.org/job/HBase-TRUNK/6256/])
HBASE-13232 ConnectionManger : Batch pool threads and metaLookup pool threads
should use different name pattern. (anoopsamjohn: rev
0f69ea409f7613484c901215d3ada21a0b8beb4f)
*
hbase-client/src/main/java/org/apache/hadoop/hbase/client/ConnectionManager.java
> ConnectionManger : Batch pool threads and metaLookup pool threads should use
> different name pattern
> ---------------------------------------------------------------------------------------------------
>
> Key: HBASE-13232
> URL: https://issues.apache.org/jira/browse/HBASE-13232
> Project: HBase
> Issue Type: Bug
> Reporter: Anoop Sam John
> Assignee: Anoop Sam John
> Priority: Trivial
> Fix For: 2.0.0, 1.1.0
>
> Attachments: HBASE-13232.patch
>
>
> This is a small issue happened with HBASE-13036. Passing different names to
> getThreadPool as nameHint but it is not been used. By checking HBASE-13219
> found this small issue.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
