[
https://issues.apache.org/jira/browse/HBASE-13036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14496561#comment-14496561
]
Hudson commented on HBASE-13036:
--------------------------------
SUCCESS: Integrated in HBase-1.1 #396 (See
[https://builds.apache.org/job/HBase-1.1/396/])
HBASE-13460. Revise the MetaLookupPool executor-related defaults (introduced in
HBASE-13036). (ddas: rev fe8658ce359b4e26cbb996115e2d843a7ef66889)
*
hbase-client/src/main/java/org/apache/hadoop/hbase/client/ConnectionManager.java
> Meta scanner should use its own threadpool
> ------------------------------------------
>
> Key: HBASE-13036
> URL: https://issues.apache.org/jira/browse/HBASE-13036
> Project: HBase
> Issue Type: Bug
> Reporter: Devaraj Das
> Assignee: Devaraj Das
> Fix For: 2.0.0, 1.1.0
>
> Attachments: 13036-1.txt, 13036-2.txt
>
>
> Currently, during region location lookups, the meta is scanned and for this
> the scanner submits a request to the thread pool of the table in question.
> Sometimes, it might happen that many scan requests are simultaneously
> submitted on the table - let's say 256, and this is the max size of the
> thread pool. Each of these scan requests would in turn submit meta scan
> requests on the same thread pool, but they will be in the queue. The meta
> scans will not happen and the original table scans would lock up. The meta
> scans should use a different thread pool.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
