[HBASE-1964] Enter temporary "safe mode" to ride over transient FS layer problems

• Type: Sub-task
• Status: Closed
• Priority: Major
• Resolution: Duplicate
• Component/s: Client
• Assignee: Unassigned
• Reporter: elsif
• Created: 09/Nov/09 19:16
• Updated: 11/Jun/22 23:10
• Resolved: 13/Apr/13 01:10

Description

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."

Issue Links

• is related to: HBASE-2108 [HA] hbase cluster should be able to ride over hdfs 'safe mode' flip and namenode restart/move