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 84FF117672 for ; Thu, 9 Oct 2014 17:52:47 +0000 (UTC) Received: (qmail 53686 invoked by uid 500); 9 Oct 2014 17:52:43 -0000 Delivered-To: apmail-hadoop-common-user-archive@hadoop.apache.org Received: (qmail 53582 invoked by uid 500); 9 Oct 2014 17:52:43 -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 53571 invoked by uid 99); 9 Oct 2014 17:52:42 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 09 Oct 2014 17:52:42 +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 sfhadoop@gmail.com designates 209.85.217.175 as permitted sender) Received: from [209.85.217.175] (HELO mail-lb0-f175.google.com) (209.85.217.175) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 09 Oct 2014 17:52:37 +0000 Received: by mail-lb0-f175.google.com with SMTP id u10so1629713lbd.6 for ; Thu, 09 Oct 2014 10:52:16 -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=pYc+6Gi+WpU/zs00ihKlMj31AbsGrUgb0+z2q7hN9V8=; b=vSMuIMQtlJ3eGOBaKKRXoQl5Nh7oEi6Mopfo+TJuOBvVkrV0O7AE/hfJFxzC9cD4xZ 0c9VNM/3JFt4+M0NpMlZSVw67q5+G1JRjO6VfLwnXeT2RtaK6bB4K9H9UGq1OqySP3zO fH7sW/SBm3i3dL0P2EdMXA1T3IgvcRDM4letBBwZPvXVwlgQaykn4jKRhzlmJLgLD2xx gzGmctv79Mty0iIRUkdRWi/sUZzcNZj/K39NI/KQaavTq8+YMXmLPHd3mN3oRtKFIae5 TutuvD1GB3smnmt5edVtzKvNeq8Md4TijrIFIYc0RjsEmZafC6e0+QwX+MwmvmOMZnfF VvuQ== MIME-Version: 1.0 X-Received: by 10.112.161.135 with SMTP id xs7mr19047944lbb.13.1412877136348; Thu, 09 Oct 2014 10:52:16 -0700 (PDT) Received: by 10.25.31.84 with HTTP; Thu, 9 Oct 2014 10:52:16 -0700 (PDT) In-Reply-To: References: Date: Thu, 9 Oct 2014 10:52:16 -0700 Message-ID: Subject: Re: Standby Namenode and Datanode coexistence From: SF Hadoop To: "user@hadoop.apache.org" Content-Type: multipart/alternative; boundary=001a11c31858d2cbbc05050117bc X-Virus-Checked: Checked by ClamAV on apache.org --001a11c31858d2cbbc05050117bc Content-Type: text/plain; charset=UTF-8 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 > > > > --001a11c31858d2cbbc05050117bc Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
You can run any of the daemons on any machine you want, yo= u just have to be aware of the trade offs you are making with RAM allocatio= n.

I am hoping this is a DEV cluster.=C2=A0 This is defi= nitely not a configuration you would want to use in production.=C2=A0 If yo= u 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.=C2=A0 But again, you should NEVER have the = NN and DN on the same machine (unless you are in a DEV cluster and experime= nting).


On Thu, Oct 9, 2014 at 4:19 AM, oc tsdb = <oc.tsdb@gmail.co= m> 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



--001a11c31858d2cbbc05050117bc--