hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jim Kellerman (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HBASE-678) hbase needs a 'safe-mode'
Date Tue, 01 Jul 2008 01:50:45 GMT

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

Jim Kellerman updated HBASE-678:

    Fix Version/s: 0.3.0
         Priority: Critical  (was: Minor)

Marking as critial for 0.3.0 because several other issues will depend on this.

> 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
>            Priority: Critical
>             Fix For: 0.3.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
> 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.

View raw message