hadoop-hdfs-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Azuryy Yu <azury...@gmail.com>
Subject Re: HDFS upgrade problem of fsImage
Date Thu, 21 Nov 2013 10:39:59 GMT
Thanks Steve,

I'd like to contribute for this JIRA. so do you mean HDFSv2 doesn't support
rolling upgrade currently?



On Thu, Nov 21, 2013 at 6:16 PM, Steve Loughran <stevel@hortonworks.com>wrote:

> Given you are asking questions on hdfs-dev rather than hadoop-user, the
> normal home of user-level questions, i'd like to extend to you the
> opportunity to help the HDFS dev team to implement rolling updates
>
> https://issues.apache.org/jira/browse/HDFS-5535
>
> design reviews, code and tests welcome
>
> -steve
>
>
> On 21 November 2013 06:27, Azuryy Yu <azuryyyu@gmail.com> wrote:
>
> > No. I don't do any upgrade before this.
> >
> > I just want to rolling upgrade HDFS to hadoop-2.2.0, any further ideas?
> > Thanks.
> >
> >
> > On Thu, Nov 21, 2013 at 1:28 PM, Vinayakumar B <vinayakumar.b@huawei.com
> > >wrote:
> >
> > > Looks like you have already have upgraded cluster.. And you are trying
> to
> > > upgrade one more time.
> > >
> > >
> > > -----Original Message-----
> > > From: Azuryy Yu [mailto:azuryyyu@gmail.com]
> > > Sent: 21 November 2013 09:49
> > > To: hdfs-dev@hadoop.apache.org; user@hadoop.apache.org
> > > Subject: HDFS upgrade problem of fsImage
> > >
> > > Hi Dear,
> > >
> > > I have a small test cluster with hadoop-2.0x, and HA configuraded, but
> I
> > > want to upgrade to hadoop-2.2.
> > >
> > > I dont't want to stop cluster during upgrade, so my steps are:
> > >
> > > 1)  on standby NN: hadoop-dameon.sh stop namenode
> > > 2)  remove HA configuration in the conf
> > > 3)   hadoop-daemon.sh start namenode -upgrade -clusterID test-cluster
> > >
> > > but Exception in the NN log, so how to upgrade and don't stop the whole
> > > cluster.
> > > Thanks.
> > >
> > >
> > > org.apache.hadoop.hdfs.server.common.InconsistentFSStateException:
> > > Directory /hdfs/name is in an inconsistent state: previous fs state
> > should
> > > not exist during upgrade. Finalize or rollback first.
> > >         at
> > >
> >
> org.apache.hadoop.hdfs.server.namenode.FSImage.doUpgrade(FSImage.java:323)
> > >         at
> > >
> > >
> >
> org.apache.hadoop.hdfs.server.namenode.FSImage.recoverTransitionRead(FSImage.java:248)
> > >         at
> > >
> > >
> >
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFSImage(FSNamesystem.java:858)
> > >         at
> > >
> > >
> >
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFromDisk(FSNamesystem.java:620)
> > >         at
> > >
> > >
> >
> org.apache.hadoop.hdfs.server.namenode.NameNode.loadNamesystem(NameNode.java:445)
> > >         at
> > >
> > >
> >
> org.apache.hadoop.hdfs.server.namenode.NameNode.initialize(NameNode.java:494)
> > >         at
> > >
> org.apache.hadoop.hdfs.server.namenode.NameNode.<init>(NameNode.java:692)
> > >         at
> > >
> org.apache.hadoop.hdfs.server.namenode.NameNode.<init>(NameNode.java:677)
> > >         at
> > >
> > >
> >
> org.apache.hadoop.hdfs.server.namenode.NameNode.createNameNode(NameNode.java:1279)
> > >         at
> > >
> org.apache.hadoop.hdfs.server.namenode.NameNode.main(NameNode.java:1345)
> > >
> >
>
> --
> 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.
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message