You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Andrew Purtell (JIRA)" <ji...@apache.org> on 2010/05/14 00:15:46 UTC
[jira] Resolved: (HBASE-2098) [EC2] Build a HA cluster
[ https://issues.apache.org/jira/browse/HBASE-2098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Purtell resolved HBASE-2098.
-----------------------------------
Resolution: Later
Closed per HBASE-2543.
> [EC2] Build a HA cluster
> ------------------------
>
> Key: HBASE-2098
> URL: https://issues.apache.org/jira/browse/HBASE-2098
> Project: Hadoop HBase
> Issue Type: Sub-task
> Reporter: Andrew Purtell
> Priority: Minor
> Fix For: 0.22.0
>
>
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.