[
https://issues.apache.org/jira/browse/HBASE-1964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Purtell updated HBASE-1964:
----------------------------------
Issue Type: Sub-task (was: Improvement)
Parent: HBASE-2183
> Enter temporary "safe mode" to ride over transient FS layer problems
> --------------------------------------------------------------------
>
> Key: HBASE-1964
> URL: https://issues.apache.org/jira/browse/HBASE-1964
> Project: Hadoop HBase
> Issue Type: Sub-task
> Components: client
> Reporter: elsif
> Assignee: Andrew Purtell
> Fix For: 0.21.0
>
>
> 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.
-
You can reply to this email to add a comment to the issue online.
