Details
-
Sub-task
-
Status: Closed
-
Minor
-
Resolution: Later
-
None
-
None
-
None
Description
The Hadoop NameNode is a single point of failure. If the master instance fails, HDFS is down; therefore, HBase as well. So we do not try to deploy HBase in a multimaster configuration for that reason. Instead we colocate the HDFS NameNode and HBase HMaster on the same instance and run with its failure as a known risk. As these EC2 scripts are starter scripts which can (and should) be customized, this is ok, but we can do better. We should deploy a fully fault tolerant Hadoop+HBase cluster as a worked example of how to do it.
Attachments
Issue Links
- is related to
-
HDFS-839 The NameNode should forward block reports to BackupNode
- Open
-
HDFS-976 Hot Standby for NameNode
- Resolved
-
HADOOP-4539 Streaming Edits to a Backup Node.
- Closed
-
HBASE-1295 Multi data center replication
- Closed
-
HBASE-2183 Ride over restart
- Closed