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 1760E10D52 for ; Fri, 30 Aug 2013 20:17:30 +0000 (UTC) Received: (qmail 38402 invoked by uid 500); 30 Aug 2013 20:17:25 -0000 Delivered-To: apmail-hadoop-user-archive@hadoop.apache.org Received: (qmail 38196 invoked by uid 500); 30 Aug 2013 20:17:24 -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 38189 invoked by uid 99); 30 Aug 2013 20:17:23 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 30 Aug 2013 20:17:23 +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 oraclehad@gmail.com designates 209.85.214.196 as permitted sender) Received: from [209.85.214.196] (HELO mail-ob0-f196.google.com) (209.85.214.196) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 30 Aug 2013 20:17:19 +0000 Received: by mail-ob0-f196.google.com with SMTP id ef5so610438obb.11 for ; Fri, 30 Aug 2013 13:16:59 -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=oWThYDxPD41ezOKfzyu8EV3r7U1Da4JgqeCSzwGL4gM=; b=0HI7BqJ4H4RJBfBhv9KwQ2k/zo4lEKaemvLN4VfGqAaW5hQBslA82RrCOiSzovBUPX zcnzkeLbU/d0kYamgOTP5zmn4UC6qn2kIVlxcSKLGr3UxoKEyiqVsyWGtIHfATkfaoDX /3yUcdgoWQ/wSuVUGsnNWN90eogM1txtETEH6aDE99LAza4PVCWlcvCArg7qbBkULDfp t7nqS6EcrriCVIHzJEFV3dc1ylgY5uggDh1PYxJ4hlAnJ2YmKQInS/RUmBk5UCca8di2 7oDIfwKY4fJ6IZXViEX4y/fkiqAM6pZrw+PiMe05aTiFvBeWZonA+oNsxEIEbbQV5n4w ZOyw== MIME-Version: 1.0 X-Received: by 10.182.129.42 with SMTP id nt10mr8166899obb.19.1377893819066; Fri, 30 Aug 2013 13:16:59 -0700 (PDT) Received: by 10.182.165.34 with HTTP; Fri, 30 Aug 2013 13:16:58 -0700 (PDT) In-Reply-To: References: Date: Sat, 31 Aug 2013 01:46:58 +0530 Message-ID: Subject: Re: hadoop 2.0.5 datanode heartbeat issue From: orahad bigdata To: user Content-Type: multipart/alternative; boundary=e89a8fb1fbfe9faf0704e52fe70d X-Virus-Checked: Checked by ClamAV on apache.org --e89a8fb1fbfe9faf0704e52fe70d Content-Type: text/plain; charset=ISO-8859-1 Thanks Jitendra, I have restarted my DataNode and suddenly it works for me :) now it's connected to both NN's. Do you know why this issue occurred? Thanks On Sat, Aug 31, 2013 at 1:24 AM, Jitendra Yadav wrote: > Hi, > > However your conf looks fine but I would say that you should restart > your DN once and check your NN weburl. > > Regards > Jitendra > > On 8/31/13, orahad bigdata wrote: > > here is my conf files. > > > > -----------core-site.xml----------- > > > > > > fs.defaultFS > > hdfs://orahadoop > > > > > > dfs.journalnode.edits.dir > > /u0/journal/node/local/data > > > > > > > > ------------ hdfs-site.xml------------- > > > > > > dfs.nameservices > > orahadoop > > > > > > dfs.ha.namenodes.orahadoop > > node1,node2 > > > > > > dfs.namenode.rpc-address.orahadoop.node1 > > clone1:8020 > > > > > > dfs.namenode.rpc-address.orahadoop.node2 > > clone2:8020 > > > > > > dfs.namenode.http-address.orahadoop.node1 > > clone1:50070 > > > > > > dfs.namenode.http-address.orahadoop.node2 > > clone2:50070 > > > > > > dfs.namenode.shared.edits.dir > > qjournal://clone3:8485;clone1:8485;clone2:8485/orahadoop > > > > > > dfs.client.failover.proxy.provider.orahadoop > > > > > org.apache.hadoop.hdfs.server.namenode.ha.ConfiguredFailoverProxyProvider > > > > > > > > --------- mapred-site.xml ------------- > > > > > > > > mapreduce.framework.name > > classic > > > > > > > > > > > > > > > > > > > > On Sat, Aug 31, 2013 at 12:21 AM, Jing Zhao > wrote: > > > >> Another possibility I can imagine is that the old configuration > >> property "fs.default.name" is still in your configuration with a > >> single NN's host+ip as its value. In that case this bad value may > >> overwrite the value of fs.defaultFS. > >> > >> It may be helpful if you can post your configurations. > >> > >> On Fri, Aug 30, 2013 at 11:32 AM, orahad bigdata > >> wrote: > >> > Thanks Jing, > >> > > >> > I'm using same configuration files at datanode side. > >> > > >> > dfs.nameservices -> orahadoop (hdfs-site.xml) > >> > > >> > fs.defaultFS -> hdfs://orahadoop (core-site.xml) > >> > > >> > Thanks > >> > On 8/30/13, Jing Zhao wrote: > >> >> You may need to make sure the configuration of your DN has also been > >> >> updated for HA. If your DN's configuration still uses the old URL > >> >> (e.g., one of your NN's host+port) for "fs.defaultFS", DN will only > >> >> connect to that NN. > >> >> > >> >> On Fri, Aug 30, 2013 at 10:56 AM, orahad bigdata < > oraclehad@gmail.com> > >> >> wrote: > >> >>> Hi All, > >> >>> > >> >>> I'm using Hadoop 2.0.5 HA with QJM, After starting the cluster I did > >> >>> some manual switch overs between NN.Then after I opened WEBUI page > >> >>> for > >> >>> both the NN, I saw some strange situation where my DN connected to > >> >>> standby NN but not sending the heartbeat to primary NameNode . > >> >>> > >> >>> please guide. > >> >>> > >> >>> Thanks > >> >> > >> >> -- > >> >> CONFIDENTIALITY NOTICE > >> >> NOTICE: This message is intended for the use of the individual or > >> entity to > >> >> > >> >> which it is addressed and may contain information that is > >> >> confidential, > >> >> privileged and exempt from disclosure under applicable law. If the > >> reader > >> >> of this message is not the intended recipient, you are hereby > notified > >> that > >> >> > >> >> any printing, copying, dissemination, distribution, disclosure or > >> >> forwarding of this communication is strictly prohibited. If you have > >> >> received this communication in error, please contact the sender > >> immediately > >> >> > >> >> and delete it from your system. Thank You. > >> >> > >> > >> -- > >> CONFIDENTIALITY NOTICE > >> NOTICE: This message is intended for the use of the individual or entity > >> to > >> which it is addressed and may contain information that is confidential, > >> privileged and exempt from disclosure under applicable law. If the > reader > >> of this message is not the intended recipient, you are hereby notified > >> that > >> any printing, copying, dissemination, distribution, disclosure or > >> forwarding of this communication is strictly prohibited. If you have > >> received this communication in error, please contact the sender > >> immediately > >> and delete it from your system. Thank You. > >> > > > --e89a8fb1fbfe9faf0704e52fe70d Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Thanks Jitendra,
=A0
I=A0have res= tarted my DataNode and suddenly it works for me :) now it's connected t= o both NN's.
=A0
Do you know why this issue occurre= d?
=A0
Thanks
=A0


On Sat, Aug 31, 2013 at 1:24 AM, Jite= ndra Yadav <jeetuyadav200890@gmail.com> wrote:
Hi,

However your conf looks fine but I would say that you should =A0restart
your DN once and check your NN weburl.

Regards
Jitendra

On 8/31/13, orahad bigdata <oracl= ehad@gmail.com> wrote:
> here is my conf files.
>
> -----------core-site.xml-----------
> <configuration>
> <property>
> =A0 <name>fs.defaultFS</name>
> =A0 <value>hdfs://orahadoop</value>
> </property>
> <property>
> =A0 <name>dfs.journalnode.edits.dir</name>
> =A0 <value>/u0/journal/node/local/data</value>
> </property>
> </configuration>
>
> ------------ hdfs-site.xml-------------
> <configuration>
> <property>
> =A0 <name>dfs.nameservices</name>
> =A0 <value>orahadoop</value>
> </property>
> <property>
> =A0 <name>dfs.ha.namenodes.orahadoop</name>
> <value>node1,node2</value>
> </property>
> <property>
> =A0 <name>dfs.namenode.rpc-address.orahadoop.node1</name><= br> > =A0 <value>clone1:8020</value>
> </property>
> <property>
> =A0 <name>dfs.namenode.rpc-address.orahadoop.node2</name><= br> > =A0 <value>clone2:8020</value>
> </property>
> <property>
> =A0 <name>dfs.namenode.http-address.orahadoop.node1</name>=
> =A0 <value>clone1:50070</value>
> </property>
> <property>
> =A0 <name>dfs.namenode.http-address.orahadoop.node2</name>=
> =A0 <value>clone2:50070</value>
> </property>
> <property>
> =A0 <name>dfs.namenode.shared.edits.dir</name>
> =A0 <value>qjournal://clone3:8485;clone1:8485;clone2:8485/orahad= oop</value>
> </property>
> <property>
> =A0 <name>dfs.client.failover.proxy.provider.orahadoop</name&= gt;
>
> <value>org.apache.hadoop.hdfs.server.namenode.ha.ConfiguredFailo= verProxyProvider</value>
> </property>
> </configuration>
>
> --------- mapred-site.xml -------------
>
> <configuration>
> <property>
> =A0 =A0 <name>mapreduce.framework.name</name>
> =A0 =A0 <value>classic</value>
> =A0 </property>
> </configuration>
>
>
>
>
>
>
>
> On Sat, Aug 31, 2013 at 12:21 AM, Jing Zhao <jing@hortonworks.com> wrote:
>
>> Another possibility I can imagine is that the old configuration >> property "fs.default.name" is still in your configuration with a
>> single NN's host+ip as its value. In that case this bad value = may
>> overwrite the value of fs.defaultFS.
>>
>> It may be helpful if you can post your configurations.
>>
>> On Fri, Aug 30, 2013 at 11:32 AM, orahad bigdata <oraclehad@gmail.com>
>> wrote:
>> > Thanks Jing,
>> >
>> > I'm using same configuration files at datanode side.
>> >
>> > dfs.nameservices -> orahadoop (hdfs-site.xml)
>> >
>> > fs.defaultFS -> hdfs://orahadoop (core-site.xml)
>> >
>> > Thanks
>> > On 8/30/13, Jing Zhao <jing@hortonworks.com> wrote:
>> >> You may need to make sure the configuration of your DN ha= s also been
>> >> updated for HA. If your DN's configuration still uses= the old URL
>> >> (e.g., one of your NN's host+port) for "fs.defau= ltFS", DN will only
>> >> connect to that NN.
>> >>
>> >> On Fri, Aug 30, 2013 at 10:56 AM, orahad bigdata <oraclehad@gmail.com>
>> >> wrote:
>> >>> Hi All,
>> >>>
>> >>> I'm using Hadoop 2.0.5 HA with QJM, After startin= g the cluster I did
>> >>> some manual switch overs between NN.Then after I open= ed WEBUI page
>> >>> for
>> >>> both the NN, I saw some strange situation where my DN= connected to
>> >>> standby NN but not sending the heartbeat to primary N= ameNode .
>> >>>
>> >>> please guide.
>> >>>
>> >>> Thanks
>> >>
>> >> --
>> >> CONFIDENTIALITY NOTICE
>> >> NOTICE: This message is intended for the use of the indiv= idual or
>> entity to
>> >>
>> >> which it is addressed and may contain information that is=
>> >> confidential,
>> >> privileged and exempt from disclosure under applicable la= w. If the
>> reader
>> >> of this message is not the intended recipient, you are he= reby notified
>> that
>> >>
>> >> any printing, copying, dissemination, distribution, discl= osure or
>> >> forwarding of this communication is strictly prohibited. = If you have
>> >> received this communication in error, please contact the = sender
>> immediately
>> >>
>> >> and delete it from your system. Thank You.
>> >>
>>
>> --
>> CONFIDENTIALITY NOTICE
>> NOTICE: This message is intended for the use of the individual or = entity
>> to
>> which it is addressed and may contain information that is confiden= tial,
>> privileged and exempt from disclosure under applicable law. If the= reader
>> of this message is not the intended recipient, you are hereby noti= fied
>> that
>> any printing, copying, dissemination, distribution, disclosure or<= br> >> forwarding of this communication is strictly prohibited. If you ha= ve
>> received this communication in error, please contact the sender >> immediately
>> and delete it from your system. Thank You.
>>
>

--e89a8fb1fbfe9faf0704e52fe70d--