Mailing-List: contact hdfs-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-dev@hadoop.apache.org
Message-ID: <55954DEC.9060200@gmail.com>
Date: Thu, 02 Jul 2015 16:42:52 +0200
From: Dmitry Salychev <darkness.bsd@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
 rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: hdfs-dev@hadoop.apache.org
Subject: Re: NameNode as a single point of failure
References: <5594D81C.5020303@gmail.com>
 <CADoWKTA6zX6FKh1gfOpsNuULe6nfbrvX7WcawYEOq9Sr538qkw@mail.gmail.com>
In-Reply-To: 
 <CADoWKTA6zX6FKh1gfOpsNuULe6nfbrvX7WcawYEOq9Sr538qkw@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit

Sure, I did. It's actually not what I'm looking for. I don't want to 
spend time to make dead NN alive by my hands. There should be a solution 
for NN-SPOF problem.

On 07/02/2015 04:36 PM, Vinayakumar B wrote:
> Hi..
> Did you look at the HDFS Namenode high availability?
>
> -Vinay
> On Jul 2, 2015 11:50 AM, "Dmitry Salychev" <darkness.bsd@gmail.com> wrote:
>
>> Hello, HDFS Developers.
>>
>> I know that NN is a single point of failure of an entire HDFS cluster. If
>> it fails, the cluster will be unavailable no matter how many DN there. I
>> know that there is an initiative <
>> http://www.wandisco.com/system/files/documentation/Meetup-ConsensusReplication.pdf>
>> which introduces ConsensusNode (as I can see it looks like distributed NN)
>> and related issues (HDFS-6469 <
>> https://issues.apache.org/jira/browse/HDFS-6469>, HADOOP-10641 <
>> https://issues.apache.org/jira/browse/HADOOP-10641> and HDFS-7007 <
>> https://issues.apache.org/jira/browse/HDFS-7007>). So, I'd like to ask.
>>
>> Has this NN-SPOF problem been solved? If it hasn't, can you show me an
>> entry point where I can help to solve it?
>>
>> Thanks for your time.
>>
>>
>>