Re: NameNode as a single point of failure

Hi Konstantin, I can not reply to you about WANdisco's proprietary system right now, I'll have to talk to our team. I'm afraid that we are not ready for paid solution, I guess. Generally, I'm looking for an entry point to contribute to Hadoop or related projects (like HDFS, and so on). I think

Re: NameNode as a single point of failure

Hey Dmitry, You understood correctly that QJM with automatic failover is the current state of the art for HDFS. With it we still have a single active NameNode on the cluster at any given time, which does not solve the performance bottleneck problem. I think active-active HA would have been an impr

Re: NameNode as a single point of failure

Not really Dmitry, QJM with automatic failover is being used in very large production clusters. So its hardly a cutting edge feature by now and if configured correctly you can failover in matter of seconds without major hiccups to the clients. -- Cloudera, Inc. On Thu, Jul 2, 2015 at 8:25 AM, D

Re: NameNode as a single point of failure

Hi, Esteban. Thanks for your reply. Thus, QJM automatic failover option is a cut-edge thing. Am I right? I think that it's a good idea to have truly equal NNs doing their work in parallel, as Konstantin Shvachko mentioned. On 07/02/2015 04:49 PM, Esteban Gutierrez wrote: Hi Dmitry, Have y

Re: NameNode as a single point of failure

Hi Dmitry, Have you looked into the QJM automatic failover mode using the ZKFailoverController? https://hadoop.apache.org/docs/r2.6.0/hadoop-project-dist/hadoop-hdfs/HDFSHighAvailabilityWithQJM.html#Automatic_Failover This is the most commonly used HA mode in production environments. Also there is

Re: NameNode as a single point of failure

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

Re: NameNode as a single point of failure

Hi.. Did you look at the HDFS Namenode high availability? -Vinay On Jul 2, 2015 11:50 AM, "Dmitry Salychev" 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 >

NameNode as a single point of failure

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 whic