Return-Path: X-Original-To: apmail-hadoop-user-archive@minotaur.apache.org Delivered-To: apmail-hadoop-user-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id BB82317E74 for ; Fri, 10 Oct 2014 19:28:43 +0000 (UTC) Received: (qmail 62824 invoked by uid 500); 10 Oct 2014 19:28:38 -0000 Delivered-To: apmail-hadoop-user-archive@hadoop.apache.org Received: (qmail 62712 invoked by uid 500); 10 Oct 2014 19:28:38 -0000 Mailing-List: contact user-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@hadoop.apache.org Delivered-To: mailing list user@hadoop.apache.org Received: (qmail 62702 invoked by uid 99); 10 Oct 2014 19:28:38 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 10 Oct 2014 19:28:38 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of manojsameltech@gmail.com designates 209.85.216.170 as permitted sender) Received: from [209.85.216.170] (HELO mail-qc0-f170.google.com) (209.85.216.170) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 10 Oct 2014 19:28:33 +0000 Received: by mail-qc0-f170.google.com with SMTP id m20so2518244qcx.29 for ; Fri, 10 Oct 2014 12:28:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=BZiWLgAMCGZ4rX/9k9M28KZGa2LRT9wVot8Q4hFdGJQ=; b=04HgRTHCnaCUH/rtDRF/IG0oF1H168P+OKLu2uWeDDAMtS1FWu8Ggokv6RfY0pxv1I /W/8D3tDcW37qx1s5pmN/qgKCqakmGhcr6wnxofZbd6t0LpGfYkYWy0Jx7RzggiNMMk5 1e2QEWmegMoL+H/GYElX0Cwy7DQdKDa9WlfcVvOr22JfyaroKlWxe+nSHYINIDrBEhCP QyxFCKAFG/oNNrbEQwGphtPEhNK+lfoF6tcUPk+5iZvpx+5BHk/hy4Bguj0ZJH4TT7CI wIV1ksudtybwJYKO4owypyAOGEzOyKKtnQk6bY9ZQTjyvIO5DLIiLW25/ki8IFW6FO26 EgiA== MIME-Version: 1.0 X-Received: by 10.140.20.3 with SMTP id 3mr11572989qgi.33.1412969292509; Fri, 10 Oct 2014 12:28:12 -0700 (PDT) Received: by 10.96.33.106 with HTTP; Fri, 10 Oct 2014 12:28:12 -0700 (PDT) In-Reply-To: References: Date: Fri, 10 Oct 2014 12:28:12 -0700 Message-ID: Subject: Re: Standby Namenode and Datanode coexistence From: Manoj Samel To: user@hadoop.apache.org Content-Type: multipart/alternative; boundary=001a11c137b8c2396d0505168c95 X-Virus-Checked: Checked by ClamAV on apache.org --001a11c137b8c2396d0505168c95 Content-Type: text/plain; charset=UTF-8 The HA namenode also should run hadoop-hdfs-zkfc which is the zookeeper failover controller for HA On Thu, Oct 9, 2014 at 11:42 PM, oc tsdb wrote: > One more query we have - > > Standby namenode should be running with all the services that are running > on active name node? or hadoop-hdfs-namenode is alone sufficient initially? > > Thanks > oc.tsdb > > On Fri, Oct 10, 2014 at 10:06 AM, oc tsdb wrote: > >> Thank you.We understood. >> >> Thanks >> oc.tsdb >> >> On Thu, Oct 9, 2014 at 11:22 PM, SF Hadoop wrote: >> >>> You can run any of the daemons on any machine you want, you just have to >>> be aware of the trade offs you are making with RAM allocation. >>> >>> I am hoping this is a DEV cluster. This is definitely not a >>> configuration you would want to use in production. If you are asking in >>> regards to a production cluster, the NNs should live apart from the >>> datanodes though it is perfectly fine to run the journal node and zookeeper >>> instances on the NNs. But again, you should NEVER have the NN and DN on >>> the same machine (unless you are in a DEV cluster and experimenting). >>> >>> >>> On Thu, Oct 9, 2014 at 4:19 AM, oc tsdb wrote: >>> >>>> Hi, >>>> >>>> We have cluster with 3 nodes (1 namenode + 2 datanodes). >>>> Cluster is running with hadoop 2.4.0 version. >>>> >>>> We would like to add High Availability(HA) to Namenode using the Quorum >>>> Journal Manager. >>>> >>>> As per the below link, we need two NN machines with same configuration. >>>> >>>> >>>> http://hadoop.apache.org/docs/r2.4.0/hadoop-project-dist/hadoop-hdfs/HDFSHighAvailabilityWithQJM.html#Hardware >>>> resources >>>> >>>> Our query is: >>>> >>>> As we have existing cluster with 3 nodes (1 namenode + 2 datanodes), >>>> can we configure standby namenode on one of the datanodes? Will there be >>>> any issues if we run standby namenode and datanode together? >>>> Or we should add one more machine and configure it as standby namenode? >>>> >>>> Regarding Journal node, Can we run it on any machine (datanode and >>>> namenode)? >>>> >>>> Thanks in advance. >>>> >>>> Thanks >>>> oc.tsdb >>>> >>>> >>>> >>>> >>> >> > --001a11c137b8c2396d0505168c95 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
The HA namenode also should run=C2=A0hadoop-hdfs-zkfc which is the zookee= per failover controller for HA

<= div class=3D"gmail_quote">On Thu, Oct 9, 2014 at 11:42 PM, oc tsdb <oc.tsd= b@gmail.com> wrote:
One more query we have -

Standby namenode shou= ld be running with all the services that are running on active name node? o= r=C2=A0hadoop-hdfs-namenode is alone sufficient initially?

Thanks
oc= .tsdb

On Fri, Oct 10, 2014 = at 10:06 AM, oc tsdb <oc.tsdb@gmail.com> wrote:
Thank you.We understood.

Thanks
oc.tsdb
=

On Thu, Oct 9, 2014 at 11:22 PM, SF Hadoop <sfhadoop@gmail.com&= gt; wrote:
You ca= n run any of the daemons on any machine you want, you just have to be aware= of the trade offs you are making with RAM allocation.

I= am hoping this is a DEV cluster.=C2=A0 This is definitely not a configurat= ion you would want to use in production.=C2=A0 If you are asking in regards= to a production cluster, the NNs should live apart from the datanodes thou= gh it is perfectly fine to run the journal node and zookeeper instances on = the NNs.=C2=A0 But again, you should NEVER have the NN and DN on the same m= achine (unless you are in a DEV cluster and experimenting).

<= /div>

= On Thu, Oct 9, 2014 at 4:19 AM, oc tsdb <oc.tsdb@gmail.com> = wrote:
= Hi,

We have cluster with 3 nodes (1 namenode + 2 datanod= es).
Cluster is running with hadoop 2.4.0 version.

=
We would like to add High Availability(HA) to Namenode using the= Quorum Journal Manager.

As per the below link, we= need two NN machines with same configuration.


Our quer= y is:

As we have existing cluster with 3 nodes (1 = namenode + 2 datanodes), can we configure standby namenode on one of the da= tanodes? Will there be any issues if we run standby namenode and datanode t= ogether?
Or we should add one more machine and configure it as st= andby namenode?

Regarding Journal node, Can we run= it on any machine (datanode and namenode)?=C2=A0

= Thanks in advance.

Thanks
oc.tsdb=C2=A0






--001a11c137b8c2396d0505168c95--