Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Message-ID: <16041672.2861271635499795.JavaMail.jira@thor>
Date: Sun, 18 Apr 2010 20:04:59 -0400 (EDT)
From: "Daniel Einspanjer (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Subject: [jira] Commented: (HDFS-1064) NN Availability - umbrella Jira
In-Reply-To: <247812383.447081269387987330.JavaMail.jira@brutus.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HDFS-1064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12858360#action_12858360 ] 

Daniel Einspanjer commented on HDFS-1064:
-----------------------------------------

I've noticed that for the current recommended configuration and for the two HDFS HA strategies I've seen, they all involve writing the NN data to NFS shared storage.  This still seems to be a single point of failure to me.  If the NFS becomes unreachable or if the NFS filer must be taken down for maintenance, where does that leave the cluster?

I was recently investigating the possibility of using RHEL GFS or something similar to provide a high availability storage location for the NN data.  It was suggested that I not take this path so I'm just trying to understand why it isn't necessary.

> NN Availability - umbrella Jira
> -------------------------------
>
>                 Key: HDFS-1064
>                 URL: https://issues.apache.org/jira/browse/HDFS-1064
>             Project: Hadoop HDFS
>          Issue Type: New Feature
>            Reporter: Sanjay Radia
>
> This is an umbrella jira for discussing availability of the HDFS NN and providing references to other Jiras that improve its availability. This includes, but is not limited to, automatic failover. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.