Mailing-List: contact hbase-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hbase-dev@hadoop.apache.org
Message-ID: <31560125.1228934444953.JavaMail.jira@brutus>
Date: Wed, 10 Dec 2008 10:40:44 -0800 (PST)
From: "stack (JIRA)" <jira@apache.org>
To: hbase-dev@hadoop.apache.org
Subject: [jira] Updated: (HBASE-1050) Allow regions to split around scanners
In-Reply-To: <1136530649.1228789424235.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

stack updated HBASE-1050:
-------------------------

         Priority: Blocker  (was: Major)
    Fix Version/s: 0.20.0

Others have reported this phenomeon on list.   Marking blocker against 0.20.0.  Gets in the way of our scaling.

> Allow regions to split around scanners
> --------------------------------------
>
>                 Key: HBASE-1050
>                 URL: https://issues.apache.org/jira/browse/HBASE-1050
>             Project: Hadoop HBase
>          Issue Type: Improvement
>          Components: client, regionserver
>            Reporter: Andrew Purtell
>            Priority: Blocker
>             Fix For: 0.20.0
>
>
> We have a number of scanners iterating over a table that also sees a lot of constant write activity. If the scans are too frequent we will suppress splitting. At a lull then a number of splits happen all at once, occasionally overwhelming DFS and causing file corruption. 
> I wonder how much work it would be to split regions around scanners. Rather than wait for scanner leases to expire, suspend/block the scanner, split the table, and then negotiate with the client to continue. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.