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 E04B8D985 for ; Thu, 22 Nov 2012 09:49:08 +0000 (UTC) Received: (qmail 65413 invoked by uid 500); 22 Nov 2012 09:49:03 -0000 Delivered-To: apmail-hadoop-user-archive@hadoop.apache.org Received: (qmail 65147 invoked by uid 500); 22 Nov 2012 09:49: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 65023 invoked by uid 99); 22 Nov 2012 09:49:01 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 22 Nov 2012 09:49:01 +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 harsh@cloudera.com designates 209.85.217.176 as permitted sender) Received: from [209.85.217.176] (HELO mail-lb0-f176.google.com) (209.85.217.176) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 22 Nov 2012 09:48:57 +0000 Received: by mail-lb0-f176.google.com with SMTP id k6so6816513lbo.35 for ; Thu, 22 Nov 2012 01:48:35 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type:x-gm-message-state; bh=IuHH2ubECPc9nJGOawS11Je8YMXLw0KNAC1LW9F798k=; b=VWC+++CoGVjqaCV/wnexuVPSsnzwtzHfvm0SbkOCoyiw9nosw4TCoiRFcLw/RKpnls oEFSLV5v01i8f6Kgm13KbA+J6xB8pzVFqw+1Y3p1P6F+yeVjQ8F8EBSsFZJaLI6O8Iak kbm/YhOXNLXtNgDCECOWORRizWWQuPFWsgevV2OTnBQvAR0iswbY+13xvhm72VVHPwTc mOSme5w7jNPq3/BrVVU9Ts65pOSFmDMmp62QvXHx8uz2mzBAcEvvj94Rypti2tqoXG/T UqLr6uqk0pKMtEE1nLhtat7O7vs0087ilhJ0Qm5C0AOIlzqlU8Ce4b7NvaxDh9jFKsFK yjAQ== Received: by 10.112.102.130 with SMTP id fo2mr386026lbb.35.1353577715520; Thu, 22 Nov 2012 01:48:35 -0800 (PST) MIME-Version: 1.0 Received: by 10.112.23.104 with HTTP; Thu, 22 Nov 2012 01:48:14 -0800 (PST) In-Reply-To: References: <1542FA4EE20C5048A5C2A3663BED2A6B30B16F27@szxeml531-mbx.china.huawei.com> From: Harsh J Date: Thu, 22 Nov 2012 15:18:14 +0530 Message-ID: Subject: Re: HADOOP UPGRADE ISSUE To: "" Content-Type: multipart/alternative; boundary=14dae9d68218e8d66604cf125ed9 X-Gm-Message-State: ALoCoQm8Ts09ZjrONCllzGIkU//4ZZE4vbsaB1nPaTdmQ1nSWrYkYjoEjcftovqvlQOMOBgTL2uz X-Virus-Checked: Checked by ClamAV on apache.org --14dae9d68218e8d66604cf125ed9 Content-Type: text/plain; charset=ISO-8859-1 Ah alright, yes you can take down the shell instance of NN you've started by issuing a simple Ctrl+C, and then start it with the other DNs, SNN in the background with the regular start-dfs or start-all command. That is safe to do. P.s. Be sure to finalize your upgrade after adequate testing has been done. You can do this at a later time. On Thu, Nov 22, 2012 at 3:00 PM, yogesh dhari wrote: > Hello Harsh.. > > Thanks for your suggestion :-), I need more guidance over it. > > Terminal through I have run command > hadoop namenode -upgrade (Say Terminal-1) > > terminal-1 got stuck at this point. > > > 12/11/22 13:06:19 INFO ipc.Server: IPC Server handler 9 on 9000: starting > ""and still cursor is blinking..."" > > Should I do stop it using ctrl+c command. If I do so it will kill the > process. > > If I do open new terminal(say Terminal-2) and run JPS it shows > 6374 NameNode > 7615 Jps > > As you mentioned to run hadoop fs -ls / > it shows all stored directories..( on Terminal-2 ) > > Now. Should I kill the process over Termial-1. What should I do to make it > complete without any loss of data.. > > I am attaching screen shot.. > > Please have a look > > > Thanks & Regards > Yogesh Kumar > > > > > > > > > ------------------------------ > From: harsh@cloudera.com > Date: Thu, 22 Nov 2012 14:14:00 +0530 > Subject: Re: HADOOP UPGRADE ISSUE > To: user@hadoop.apache.org > > > If your UI is already up, then NN is already functional. The UI merely > shows that your upgrade is done but has not been manually finalized by you > (leaving it open for a rollback if needed). > > You could try a simple "hadoop fs -ls /" to see if NN is functional, run > some other regular job based tests of yours, and then finalize the new > format by issuing "hadoop dfsadmin -finalizeUpgrade" to make the upgrade > permanent (no rollback possible after this). > > > On Thu, Nov 22, 2012 at 1:49 PM, yogesh dhari wrote: > > Thanks Uma, > > I used command > hadoop namenode -upgrade and its started well but got stuck at one point. > > 12/11/22 13:06:19 INFO mortbay.log: Started > SelectChannelConnector@localhost:50070 > 12/11/22 13:06:19 INFO namenode.NameNode: Web-server up at: localhost:50070 > 12/11/22 13:06:19 INFO ipc.Server: IPC Server Responder: starting > 12/11/22 13:06:19 INFO ipc.Server: IPC Server listener on 9000: starting > 12/11/22 13:06:19 INFO ipc.Server: IPC Server handler 0 on 9000: starting > 12/11/22 13:06:19 INFO ipc.Server: IPC Server handler 1 on 9000: starting > 12/11/22 13:06:19 INFO ipc.Server: IPC Server handler 2 on 9000: starting > 12/11/22 13:06:19 INFO ipc.Server: IPC Server handler 3 on 9000: starting > 12/11/22 13:06:19 INFO ipc.Server: IPC Server handler 4 on 9000: starting > 12/11/22 13:06:19 INFO ipc.Server: IPC Server handler 5 on 9000: starting > 12/11/22 13:06:19 INFO ipc.Server: IPC Server handler 6 on 9000: starting > 12/11/22 13:06:19 INFO ipc.Server: IPC Server handler 7 on 9000: starting > 12/11/22 13:06:19 INFO ipc.Server: IPC Server handler 8 on 9000: starting > 12/11/22 13:06:19 INFO ipc.Server: IPC Server handler 9 on 9000: starting > > from this point its not showing any progress for past 30 + mins... > > > and Web ui shows > > NameNode 'localhost:9000' Started: Thu Nov 22 13:06:17 IST 2012 Version: 1.0.4, > r1393290 Compiled: Wed Oct 3 05:13:58 UTC 2012 by hortonfo Upgrades: Upgrade > for version -32 has been completed. Upgrade is not finalized. > > Please suggest > > Regards > Yogesh Kumar > > > > > ------------------------------ > From: maheswara@huawei.com > To: user@hadoop.apache.org > Subject: RE: HADOOP UPGRADE ISSUE > Date: Thu, 22 Nov 2012 07:05:51 +0000 > > > start-all.sh will not carry any arguments to pass to nodes. > Start with start-dfs.sh > or start directly namenode with upgrade option. ./hadoop namenode -upgrade > > Regards, > Uma > ------------------------------ > *From:* yogesh dhari [yogeshdhari@live.com] > *Sent:* Thursday, November 22, 2012 12:23 PM > *To:* hadoop helpforoum > *Subject:* HADOOP UPGRADE ISSUE > > Hi All, > > I am trying upgrading apache *hadoop-0.20.2 to hadoop-1.0.4*. > I have give same dfs.name.dir, etc as same in hadoop-1.0.4' conf files as > were in hadoop-0.20.2. > Now I am starting dfs n mapred using > > *start-all.sh -upgrade* > > but *namenode *and *datanode* fail to run. > > 1) *Namenode's *logs shows:: > > ERROR org.apache.hadoop.hdfs.server.namenode.FSNamesystem: FSNamesystem > initialization failed. > java.io.IOException: > File system image contains an old layout version -18. > An upgrade to version -32 is required. > Please restart NameNode with -upgrade option. > . > . > ERROR org.apache.hadoop.hdfs.server.namenode.NameNode: > java.io.IOException: > File system image contains an old layout version -18. > An upgrade to version -32 is required. > Please restart NameNode with -upgrade option. > > > 2)* Datanode's* logs shows:: > > WARN org.apache.hadoop.hdfs.server.datanode.DataNode: Invalid directory in > dfs.data.dir: Incorrect permission for /opt/hadoop_newdata_dirr, expected: > rwxr-xr-x, while actual: rwxrwxrwx > ****( how these file permission showing warnings)***** > > 2012-11-22 12:05:21,157 ERROR > org.apache.hadoop.hdfs.server.datanode.DataNode: All directories in > dfs.data.dir are invalid. > > Please suggest > > Thanks & Regards > Yogesh Kumar > > > > > > -- > Harsh J > -- Harsh J --14dae9d68218e8d66604cf125ed9 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Ah alright, yes you can take down the shell instance of NN you've start= ed by issuing a simple Ctrl+C, and then start it with the other DNs, SNN in= the background with the regular start-dfs or start-all command. That is sa= fe to do.

P.s. Be sure to finalize your upgrade after adequate testing= has been done. You can do this at a later time.


On Thu, Nov 22, 2012 at 3:00 PM, y= ogesh dhari <yogeshdhari@live.com> wrote:
Hello Harsh..

Thanks for your suggestion :-), I need more guidance o= ver it.

Terminal through I have run command
hadoop namenode -upg= rade (Say Terminal-1)

terminal-1 got stuck at this point.


12/11/22 13:06:19 INFO ipc.Server: IPC Server handler 9 on 9000: st= arting
""and still cursor is blinking...""
=
Should I do stop it using ctrl+c command.=A0 If I do so it will kill th= e process.

If I do open new terminal(say Terminal-2) and run JPS it shows
6374 = NameNode
7615 Jps

As you mentioned to run hadoop fs -ls /
it s= hows all stored directories..( on Terminal-2 )
=A0
Now. Should I kill= the process over Termial-1. What should I do to make it complete without a= ny loss of data..

I am attaching screen shot..=A0

Please have a look


= Thanks & Regards
Yogesh Kumar








From: harsh@cloudera.com
Date: Thu, 22 Nov 2012 14:14:00 +0530
Subject: Re: HADOOP UPGRADE ISSUE<= br>To: user@had= oop.apache.org


If your UI is already up, then NN is al= ready functional. The UI merely shows that your upgrade is done but has not= been manually finalized by you (leaving it open for a rollback if needed).=

You could try a simple "hadoop fs -ls /" to see if= NN is functional, run some other regular job based tests of yours, and the= n finalize the new format by issuing "hadoop dfsadmin -finalizeUpgrade= " to make the upgrade permanent (no rollback possible after this).


On Thu, Nov 22, 2012 at 1:49 PM, yogesh dhari <yoge= shdhari@live.com> wrote:
Thanks Uma,

I used command
hadoop namenode -upgrade and its star= ted well but got stuck at one point.

12/11/22 13:06:19 INFO mortbay.= log: Started SelectChannelConnector@localhost:50070
12/11/22 13:06:19 IN= FO namenode.NameNode: Web-server up at: localhost:50070
12/11/22 13:06:19 INFO ipc.Server: IPC Server Responder: starting
12/11/= 22 13:06:19 INFO ipc.Server: IPC Server listener on 9000: starting
12/11= /22 13:06:19 INFO ipc.Server: IPC Server handler 0 on 9000: starting
12/11/22 13:06:19 INFO ipc.Server: IPC Server handler 1 on 9000: starting12/11/22 13:06:19 INFO ipc.Server: IPC Server handler 2 on 9000: starting=
12/11/22 13:06:19 INFO ipc.Server: IPC Server handler 3 on 9000: starti= ng
12/11/22 13:06:19 INFO ipc.Server: IPC Server handler 4 on 9000: starting12/11/22 13:06:19 INFO ipc.Server: IPC Server handler 5 on 9000: starting=
12/11/22 13:06:19 INFO ipc.Server: IPC Server handler 6 on 9000: starti= ng
12/11/22 13:06:19 INFO ipc.Server: IPC Server handler 7 on 9000: starting12/11/22 13:06:19 INFO ipc.Server: IPC Server handler 8 on 9000: starting=
12/11/22 13:06:19 INFO ipc.Server: IPC Server handler 9 on 9000: starti= ng

from this point its not showing any progress for past 30 + mins...
<= br>
and Web ui shows

NameNode 'localhost:9000' =20
Started: Thu Nov 22 13:06:17 IST 2012
Version: 1.0.4, r1393290
Compiled: Wed Oct 3 05:13:58 UTC 2012 by hor= tonfo
Upgrades: Upgrade for version -32 has been co= mpleted. Upgrade is not finalized.


Please suggest
Regards
Yogesh Kumar




From: = maheswara@huawei.= com
To: user@hadoop= .apache.org
Subject: RE: HADOOP UPGRADE ISSUE
Date: Thu, 22 Nov 2= 012 07:05:51 +0000


start-all.sh will not carry any arguments to pass to nodes.
Start=A0with start-dfs.sh=A0
or=A0start directly=A0namenode with upgrade option.=A0./hadoop namenode -up= grade
=A0
Regards,
Uma
Fro= m: yogesh dhari [yogeshdhari@live.com]
Sent: Thursday, November 22, 2012 12:23 PM
To: hadoop helpforoum
Subject: HADOOP UPGRADE ISSUE

Hi All,

I am trying upgrading apache hadoop-0.20.2 to hadoop-1.0.4.
I have give same dfs.name.dir, etc as same in hadoop-1.0.4' conf files = as were in hadoop-0.20.2.
Now I am starting dfs n mapred using

start-all.sh -upgrade

but namenode and datanode fail to run.

1) Namenode's logs shows::

ERROR org.apache.hadoop.hdfs.server.namenode.FSNamesystem: FSNamesystem ini= tialization failed.
java.io.IOException:
File system image contains an old layout version -18.
An upgrade to version -32 is required.
Please restart NameNode with -upgrade option.
.
.
ERROR org.apache.hadoop.hdfs.server.namenode.NameNode: java.io.IOException:=
File system image contains an old layout version -18.
An upgrade to version -32 is required.
Please restart NameNode with -upgrade option.


2) Datanode's logs shows::

WARN org.apache.hadoop.hdfs.server.datanode.DataNode: Invalid directory in = dfs.data.dir: Incorrect permission for /opt/hadoop_newdata_dirr, expected: = rwxr-xr-x, while actual: rwxrwxrwx
****(=A0 how these file permission showing warnings)*****

2012-11-22 12:05:21,157 ERROR org.apache.hadoop.hdfs.server.datanode.DataNo= de: All directories in dfs.data.dir are invalid.

Please suggest

Thanks & Regards
Yogesh Kumar





--
Harsh J



--
Harsh J
--14dae9d68218e8d66604cf125ed9--