hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-13036) Meta scanner should use its own threadpool
Date Wed, 18 Feb 2015 20:43:12 GMT

    [ https://issues.apache.org/jira/browse/HBASE-13036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14326521#comment-14326521

Hudson commented on HBASE-13036:

FAILURE: Integrated in HBase-1.1 #196 (See [https://builds.apache.org/job/HBase-1.1/196/])
HBASE-13036. Meta scanner should use its own threadpool (ddas: rev e8a34fb3845ddce36dc3aa2afc0b5f7fce62a77d)
* hbase-server/src/test/java/org/apache/hadoop/hbase/client/TestMetaWithReplicas.java
* hbase-client/src/main/java/org/apache/hadoop/hbase/client/HTable.java
* 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: 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

View raw message