Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Wed, 18 Feb 2015 19:02:12 +0000 (UTC)
From: "Devaraj Das (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12774762.1423790299000.78821.1424286132740@Atlassian.JIRA>
In-Reply-To: <JIRA.12774762.1423790299000@Atlassian.JIRA>
References: <JIRA.12774762.1423790299000@Atlassian.JIRA>
 <JIRA.12774762.1423790299545@arcas>
Subject: [jira] [Updated] (HBASE-13036) Meta scanner should use its own
 threadpool
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Devaraj Das updated HBASE-13036:
--------------------------------
       Resolution: Fixed
    Fix Version/s: 1.1.0
           Status: Resolved  (was: Patch Available)

Thanks [~apurtell] & [~stack] for reviews. Committed the patch.

> 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
(v6.3.4#6332)