Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Sat, 13 Apr 2013 01:09:15 +0000 (UTC)
From: "Andrew Purtell (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12440202.1257794165894.161267.1365815355506@arcas>
In-Reply-To: <JIRA.12440202.1257794165894@arcas>
References: <JIRA.12440202.1257794165894@arcas>
Subject: [jira] [Commented] (HBASE-1964) Enter temporary "safe mode" to ride
 over transient FS layer problems
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HBASE-1964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13630844#comment-13630844 ] 

Andrew Purtell commented on HBASE-1964:
---------------------------------------

Superseded by HBASE-8338 and related.
                
> Enter temporary "safe mode" to ride over transient FS layer problems
> --------------------------------------------------------------------
>
>                 Key: HBASE-1964
>                 URL: https://issues.apache.org/jira/browse/HBASE-1964
>             Project: HBase
>          Issue Type: Sub-task
>          Components: Client
>            Reporter: elsif 
>
> When a hadoop/hbase cluster is under heavy load it will inevitably reach a tipping point where data is lost or corrupted.  A
> graceful method is needed to put the cluster into safe mode until more resources can be added or the load on the cluster has been
> reduced.  
> St.Ack has suggested the following short-term task: "Meantime, it should be possible to have a cron run a script that checks
> cluster resources from time-to-time -- e.g. how full hdfs is, how much each regionserver is carrying -- and when it determines the needle is in the red,
> flip the cluster to be read-only."

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira