Return-Path: X-Original-To: apmail-hadoop-common-user-archive@www.apache.org Delivered-To: apmail-hadoop-common-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 039D817367 for ; Fri, 10 Oct 2014 06:43:11 +0000 (UTC) Received: (qmail 92295 invoked by uid 500); 10 Oct 2014 06:43:02 -0000 Delivered-To: apmail-hadoop-common-user-archive@hadoop.apache.org Received: (qmail 92171 invoked by uid 500); 10 Oct 2014 06:43:02 -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 92161 invoked by uid 99); 10 Oct 2014 06:43:02 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 10 Oct 2014 06:43:02 +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 (nike.apache.org: domain of oc.tsdb@gmail.com designates 209.85.220.179 as permitted sender) Received: from [209.85.220.179] (HELO mail-vc0-f179.google.com) (209.85.220.179) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 10 Oct 2014 06:42:35 +0000 Received: by mail-vc0-f179.google.com with SMTP id im17so2193695vcb.10 for ; Thu, 09 Oct 2014 23:42:34 -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=Z9+vm9BQFFvy8FJdvbIVS2IihjBhO+U+4rvXZ3Ma2e4=; b=sWE8Z7gx9LX8duLuMAqq7WGmtrUUueH5YGJztz6GJsRyL71Ccfnta/PJm9vezHGOlU ax98d+xFoWPK0ZowTL+9fj9pGdsLpM+k4isNOeLRDdTTECOZp5ocY8lVfuPzVLGxKxMO j2ITL1mCi1k1yXbmFG8ym1u39kUfoom/VBTsE2QJKPFCFaZfNfcj3AMdl2RA/q9XE7ZV oB32W/1w8DiuxHwZjtD2YiNSbx43RA3hHh2Ozhc5gXgrdRi5eerteQl/IYbNzN2qlx/c SCcO8kuvUYBu9KtxNaxSQH/mLUUR0XOmeTTx+SDWFcIBgQFQdVCGxcxjSOnZSA242S3Q tXrw== MIME-Version: 1.0 X-Received: by 10.52.144.195 with SMTP id so3mr2502425vdb.14.1412923354421; Thu, 09 Oct 2014 23:42:34 -0700 (PDT) Received: by 10.220.130.137 with HTTP; Thu, 9 Oct 2014 23:42:34 -0700 (PDT) In-Reply-To: References: Date: Fri, 10 Oct 2014 12:12:34 +0530 Message-ID: Subject: Re: Standby Namenode and Datanode coexistence From: oc tsdb To: user@hadoop.apache.org Content-Type: multipart/alternative; boundary=bcaec51a7d2ca2a0d805050bda8b X-Virus-Checked: Checked by ClamAV on apache.org --bcaec51a7d2ca2a0d805050bda8b Content-Type: text/plain; charset=UTF-8 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 >>> >>> >>> >>> >> > --bcaec51a7d2ca2a0d805050bda8b Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
One more query we have -

Standby nameno= de should be running with all the services that are running on active name = node? or=C2=A0hadoop-hdfs-namenode is alone sufficient initially?

Thanks
oc.tsdb

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

Thanks
oc.tsdb

On Thu, Oct 9, 2014 at 11:22 PM, SF Hadoo= p <sfhadoop@gmail.com> wrote:
You can run any of the daemons on any machine you wan= t, you just have to be aware of the trade offs you are making with RAM allo= cation.

I am hoping this is a DEV cluster.=C2=A0 This is= definitely not a configuration you would want to use in production.=C2=A0 = If you are asking in regards to a production cluster, the NNs should live a= part from the datanodes though 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 machine (unless you are in a DEV cluster and exp= erimenting).


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

We have cluster with 3 n= odes (1 namenode + 2 datanodes).
Cluster is running with hadoop 2= .4.0 version.

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

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

=

Our query is:

As we have exist= ing cluster with 3 nodes (1 namenode + 2 datanodes), can we configure stand= by namenode on one of the datanodes? Will there be any issues if we run sta= ndby namenode and datanode together?
Or we should add one more ma= chine and configure it as standby namenode?

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

Thanks in advance.

Th= anks
oc.tsdb=C2=A0






--bcaec51a7d2ca2a0d805050bda8b--