Mailing-List: contact hbase-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hbase-dev@hadoop.apache.org
Message-ID: <1676227979.1226444744334.JavaMail.jira@brutus>
Date: Tue, 11 Nov 2008 15:05:44 -0800 (PST)
From: "Jim Kellerman (JIRA)" <jira@apache.org>
To: hbase-dev@hadoop.apache.org
Subject: [jira] Resolved: (HBASE-678) hbase needs a 'safe-mode'
In-Reply-To: <535107581.1213136385076.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-678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jim Kellerman resolved HBASE-678.
---------------------------------

    Resolution: Fixed

All tasks completed. Resolving issue.

> hbase needs a 'safe-mode'
> -------------------------
>
>                 Key: HBASE-678
>                 URL: https://issues.apache.org/jira/browse/HBASE-678
>             Project: Hadoop HBase
>          Issue Type: Improvement
>            Reporter: stack
>            Assignee: Jim Kellerman
>            Priority: Blocker
>             Fix For: 0.19.0
>
>
> Internally we have a cluster of thousands of regions.  We just did a hbase restart w/ master on new node.  Just so happened that one of the regionservers was running extra slow (was downloaded by other processes).  Meant that its portion of the assigments was taking a long time to come up...  While these regions were stuck in deploy mode, the cluster is not useable.
> We need a sort of 'safe-mode' in hbase where clients fail if they try to attach to a cluster not yet fully up.  UI should show when all assignments have been successfully made so admin can at least see when they have a problematic regionserver in their midst.

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