Mailing-List: contact hbase-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hbase-dev@hadoop.apache.org
Message-ID: <783563515.1247774414792.JavaMail.jira@brutus>
Date: Thu, 16 Jul 2009 13:00:14 -0700 (PDT)
From: "Jonathan Gray (JIRA)" <jira@apache.org>
To: hbase-dev@hadoop.apache.org
Subject: [jira] Commented: (HBASE-1583) Start/Stop of large cluster
 untenable
In-Reply-To: <2094681343.1245892027366.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-1583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12732122#action_12732122 ] 

Jonathan Gray commented on HBASE-1583:
--------------------------------------

Looks good to me.

> Start/Stop of large cluster untenable
> -------------------------------------
>
>                 Key: HBASE-1583
>                 URL: https://issues.apache.org/jira/browse/HBASE-1583
>             Project: Hadoop HBase
>          Issue Type: Bug
>            Reporter: stack
>            Assignee: stack
>             Fix For: 0.20.0
>
>         Attachments: 1583-nocompactonclose.patch, 1583-v2-nocompactonopenclose.patch
>
>
> Starting and stopping a loaded large cluster is way too flakey and takes too long.  This is 0.19.x but same issues apply to TRUNK I'd say.
> At pset with our > 100 nodes carrying 6k regions:
> + shutdown takes way too long.... maybe ten minutes or so.  We compact regions inline with shutdown.  We should just go down.  It doesn't seem like all regionservers go down everytime either.
> + startup is a mess with our assigning out regions an rebalancing at same time.  By time that the compactions on open run, it can be near an hour before whole thing settles down and becomes useable

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