hadoop-hdfs-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Uma Maheswara Rao G <hadoop....@gmail.com>
Subject Re: NameNode be formated while namenode is running
Date Wed, 15 Jan 2014 03:47:14 GMT
Seems like you are hitting https://issues.apache.org/jira/browse/HDFS-1690 ?


On Wed, Jan 15, 2014 at 6:58 AM, Stanley Shi <sshi@gopivotal.com> wrote:

> Thanks Konstantin!
> I am running on vsphere VM with CentOS64 installed, Local file system is
> ext3;
>
> Regards,
> *Stanley Shi,*
>
>
>
> On Wed, Jan 15, 2014 at 8:27 AM, Konstantin Shvachko
> <shv.hadoop@gmail.com>wrote:
>
> > Yes format should check "in_use.lock".
> > What is your environment?
> > Does it support locks on you local file system?
> >
> > Thanks,
> > --Konst
> >
> >
> > On Tue, Jan 14, 2014 at 1:38 AM, Stanley Shi <sshi@gopivotal.com> wrote:
> >
> > > Hi,
> > >
> > > I have encountered this case in my environment:
> > >
> > > 1. NameNode is actively running without any problem;
> > >
> > > 2. someone accidentally formatted the namenode (even if there's one
> > > instance running);
> > >
> > > 3. The running namenode continues to write edit log starting from some
> > big
> > > txid;
> > >
> > >
> > > This caused the namenode now in an in-consistent state:
> > >
> > > It has edit log and fsimage but if you restart the namenode, it will
> say
> > > the namenode cannot be started because it expect some txid 1 ;
> > >
> > > I think this is a bug. At least when formating the namenode, it should
> > > check if there's an namenode instance already running.
> > >
> > > Regards,
> > > *Stanley Shi,*
> > >
> >
>

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