HDFS upgrade

[Amit Sela]

Hi all,

I want to upgrade a 1TB cluster from hadoop 0.20.3 to hadoop 1.0.3.

I am interested to know how long does the hdfs upgrade take and in general
how long it takes from deploying new versions until the cluster is back to
running heavy MapReduce ?

I'd also appreciate it if someone could elaborate about how the hdfs file
system is actually executed - I read in the book tat data is not replicated
but the DNs use hard links.

Thanks,

HDFS upgrade

[Amit Sela]

Hi all,

I want to upgrade a 1TB cluster from hadoop 0.20.3 to hadoop 1.0.3.

I am interested to know how long does the hdfs upgrade take and in general
how long it takes from deploying new versions until the cluster is back to
running heavy MapReduce ?

I'd also appreciate it if someone could elaborate about how the hdfs file
system is actually executed - I read in the book tat data is not replicated
but the DNs use hard links.

Thanks,

HDFS upgrade under HA

[Azuryy Yu]

Hi,

The layout version is -43 until 2.0.4-alpha, but HDFS-4908 changed layout
version to -45.

so if My test cluster is running hadoop-2.0.4-alpha(-43), which is upgraded
from hadoop-1.0.4, then I want to upgrade using trunk(-45), how to do?

It cannot upgrade under HA, so I can use hadoop-1.0.4 core-site and
hdfs-site, then "start-dfs.sh -upgrade", but standby NN cannot upgrade,

so how to upgrade standby NN under HA?

HDFS upgrade skip versions?

[Chad William Seys]

Hi all,
  Is it required or highly recommended that one not skip between HDFS 
(hadoop) versions?

  I tried skipping from 2.6 to 2.10 and it didn't work so well. :/
  Actually, I tested this with a tiny cluster and it worked, but on the 
production cluster the datanodes did not report blocks to the namenodes. 
 (Did report storage and connectivity otherwise.)


Chad.

-
To unsubscribe, e-mail: user-unsubscr...@hadoop.apache.org
For additional commands, e-mail: user-h...@hadoop.apache.org

Re: HDFS upgrade under HA

[Suresh Srinivas]

I have hard time understanding your question.



On Fri, Jun 21, 2013 at 12:16 AM, Azuryy Yu  wrote:

> Hi,
>
> The layout version is -43 until 2.0.4-alpha, but HDFS-4908 changed layout
> version to -45.
>
> so if My test cluster is running hadoop-2.0.4-alpha(-43), which is
> upgraded from hadoop-1.0.4, then I want to upgrade using trunk(-45), how to
> do?
>

Layout version can increase (or decrease given it is negative number) by
more than 1, when you upgrade to a new release. So 2.0.4-alpha(-43) can
upgrade to trunk(-45) version.


>
> It cannot upgrade under HA, so I can use hadoop-1.0.4 core-site and
> hdfs-site, then "start-dfs.sh -upgrade", but standby NN cannot upgrade,
>

What is preventing you from upgrading? Please add details on what you are
doing and what issue you are seeing.

Regards,
Suresh

HDFS upgrade problem of fsImage

[Azuryy Yu]

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.(NameNode.java:692)
at
org.apache.hadoop.hdfs.server.namenode.NameNode.(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)

Re: HDFS upgrade skip versions?

[Wei-Chiu Chuang]

Probably one of the protobuf incompatibility. Unfortunately we don't have
an open source tool to detect protobuf incompat.

A few related issues:

   1. HDFS-15700 
   2.
  1. HDFS-14726 
 2.
1. HDFS-13371 
 1. HDFS-15660 
  2. I know folks upgraded from 2.7 to 2.10 (LinkedIn?), and 2.8 to
  2.10 (Verizon Media).
  3. Searched JIRA I don't see a known bug between 2.6 and 2.10 in the
  DN heartbeat protobuf.


On Mon, Dec 14, 2020 at 10:57 PM Chad William Seys
 wrote:

> Hi all,
>Is it required or highly recommended that one not skip between HDFS
> (hadoop) versions?
>I tried skipping from 2.6 to 2.10 and it didn't work so well. :/
>Actually, I tested this with a tiny cluster and it worked, but on the
> production cluster the datanodes did not report blocks to the namenodes.
>   (Did report storage and connectivity otherwise.)
>
> Chad.
>
> -
> To unsubscribe, e-mail: user-unsubscr...@hadoop.apache.org
> For additional commands, e-mail: user-h...@hadoop.apache.org
>
>

New data on unfinalized hdfs upgrade

[krispyjala]

What happens if you upgrade 1.0.4 to 2.2, run some stuff that puts in new
data while the upgrade is not finalized, but then revert back to 1.0.4? Will
the new data also be reverted back to 1.0.4 safely?



--
View this message in context: 
http://hadoop-common.472056.n3.nabble.com/New-data-on-unfinalized-hdfs-upgrade-tp4029496.html
Sent from the Users mailing list archive at Nabble.com.

Re: HDFS upgrade problem of fsImage

[Joshi, Rekha]

Hi Azurry,

This error occurs when FSImage finds previous fs state, and as log states you 
would need to either finalizeUpgrade or rollback to proceed.Below -

bin/hadoop dfsadmin –finalizeUpgrade
hadoop dfsadmin –rollback

On side note for a small test cluster on which one might suspect you are the 
only user, why wouldn't you insist on hot upgrade? :-)

Thanks
Rekha


Some helpful guidelines for upgrade here -

http://wiki.apache.org/hadoop/Hadoop_Upgrade

https://twiki.grid.iu.edu/bin/view/Storage/HadoopUpgrade

http://hadoop.apache.org/docs/current/hadoop-project-dist/hadoop-hdfs/Federation.html#Upgrading_from_older_release_to_0.23_and_configuring_federation


From: Azuryy Yu mailto:azury...@gmail.com>>
Reply-To: "user@hadoop.apache.org<mailto:user@hadoop.apache.org>" 
mailto:user@hadoop.apache.org>>
Date: Thursday 21 November 2013 9:48 AM
To: "hdfs-...@hadoop.apache.org<mailto:hdfs-...@hadoop.apache.org>" 
mailto:hdfs-...@hadoop.apache.org>>, 
"user@hadoop.apache.org<mailto:user@hadoop.apache.org>" 
mailto: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.(NameNode.java:692)
at 
org.apache.hadoop.hdfs.server.namenode.NameNode.(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)

Re: HDFS upgrade problem of fsImage

[Azuryy Yu]

Thanks Joshi,

I don't have upgrade before. the test cluser is the new cluster with
hadoop-2.0.3. so I don't need to 'bin/hadoop dfsadmin –finalizeUpgrade'




On Thu, Nov 21, 2013 at 7:22 PM, Joshi, Rekha wrote:

>  Hi Azurry,
>
> This error occurs when FSImage finds previous fs state, and as log states you 
> would need to either finalizeUpgrade or rollback to proceed.Below -
>
> bin/hadoop dfsadmin –finalizeUpgrade
> hadoop dfsadmin –rollback
>
> On side note for a small test cluster on which one might suspect you are the 
> only user, why wouldn't you insist on hot upgrade? :-)
>
> Thanks
> Rekha
>
> Some helpful guidelines for upgrade here -
>
> http://wiki.apache.org/hadoop/Hadoop_Upgrade
>
> https://twiki.grid.iu.edu/bin/view/Storage/HadoopUpgrade
>
> http://hadoop.apache.org/docs/current/hadoop-project-dist/hadoop-hdfs/Federation.html#Upgrading_from_older_release_to_0.23_and_configuring_federation
>
>
>   From: Azuryy Yu 
> Reply-To: "user@hadoop.apache.org" 
> Date: Thursday 21 November 2013 9:48 AM
> To: "hdfs-...@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.(NameNode.java:692)
> at
> org.apache.hadoop.hdfs.server.namenode.NameNode.(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)
>

Re: HDFS upgrade problem of fsImage

[Azuryy Yu]

I insist hot upgrade on the test cluster because I want hot upgrade on the
prod cluster.
 On 2013-11-21 7:23 PM, "Joshi, Rekha"  wrote:

>  Hi Azurry,
>
> This error occurs when FSImage finds previous fs state, and as log states you 
> would need to either finalizeUpgrade or rollback to proceed.Below -
>
> bin/hadoop dfsadmin –finalizeUpgrade
> hadoop dfsadmin –rollback
>
> On side note for a small test cluster on which one might suspect you are the 
> only user, why wouldn't you insist on hot upgrade? :-)
>
> Thanks
> Rekha
>
> Some helpful guidelines for upgrade here -
>
> http://wiki.apache.org/hadoop/Hadoop_Upgrade
>
> https://twiki.grid.iu.edu/bin/view/Storage/HadoopUpgrade
>
> http://hadoop.apache.org/docs/current/hadoop-project-dist/hadoop-hdfs/Federation.html#Upgrading_from_older_release_to_0.23_and_configuring_federation
>
>
>   From: Azuryy Yu 
> Reply-To: "user@hadoop.apache.org" 
> Date: Thursday 21 November 2013 9:48 AM
> To: "hdfs-...@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.(NameNode.java:692)
> at
> org.apache.hadoop.hdfs.server.namenode.NameNode.(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)
>

Re: HDFS upgrade problem of fsImage

[Joshi, Rekha]

Yes realized that and I see your point :-) However seems like some fs 
inconsistency present, did you attempt rollback/finalizeUpgrade and check?

For that error, FSImage.java/code finds a previous fs state -

// Upgrade is allowed only if there are

// no previous fs states in any of the directories

for (Iterator it = storage.dirIterator(); it.hasNext();) {

  StorageDirectory sd = it.next();

  if (sd.getPreviousDir().exists())

throw new InconsistentFSStateException(sd.getRoot(),

"previous fs state should not exist during upgrade. "

+ "Finalize or rollback first.");

}


Thanks

Rekha


From: Azuryy Yu mailto:azury...@gmail.com>>
Reply-To: "user@hadoop.apache.org<mailto:user@hadoop.apache.org>" 
mailto:user@hadoop.apache.org>>
Date: Thursday 21 November 2013 5:19 PM
To: "user@hadoop.apache.org<mailto:user@hadoop.apache.org>" 
mailto:user@hadoop.apache.org>>
Cc: "hdfs-...@hadoop.apache.org<mailto:hdfs-...@hadoop.apache.org>" 
mailto:hdfs-...@hadoop.apache.org>>
Subject: Re: HDFS upgrade problem of fsImage


I insist hot upgrade on the test cluster because I want hot upgrade on the prod 
cluster.

On 2013-11-21 7:23 PM, "Joshi, Rekha" 
mailto:rekha_jo...@intuit.com>> wrote:

Hi Azurry,

This error occurs when FSImage finds previous fs state, and as log states you 
would need to either finalizeUpgrade or rollback to proceed.Below -

bin/hadoop dfsadmin –finalizeUpgrade
hadoop dfsadmin –rollback

On side note for a small test cluster on which one might suspect you are the 
only user, why wouldn't you insist on hot upgrade? :-)

Thanks
Rekha


Some helpful guidelines for upgrade here -

http://wiki.apache.org/hadoop/Hadoop_Upgrade

https://twiki.grid.iu.edu/bin/view/Storage/HadoopUpgrade

http://hadoop.apache.org/docs/current/hadoop-project-dist/hadoop-hdfs/Federation.html#Upgrading_from_older_release_to_0.23_and_configuring_federation


From: Azuryy Yu mailto:azury...@gmail.com>>
Reply-To: "user@hadoop.apache.org<mailto:user@hadoop.apache.org>" 
mailto:user@hadoop.apache.org>>
Date: Thursday 21 November 2013 9:48 AM
To: "hdfs-...@hadoop.apache.org<mailto:hdfs-...@hadoop.apache.org>" 
mailto:hdfs-...@hadoop.apache.org>>, 
"user@hadoop.apache.org<mailto:user@hadoop.apache.org>" 
mailto: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.(NameNode.java:692)
at 
org.apache.hadoop.hdfs.server.namenode.NameNode.(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)

Re: HDFS upgrade problem of fsImage

[Azuryy Yu]

Thanks Joshi,

Maybe I pasted wrong log messages.

please looked at here for the real story.

https://issues.apache.org/jira/browse/HDFS-5550




On Fri, Nov 22, 2013 at 6:25 PM, Joshi, Rekha wrote:

>  Yes realized that and I see your point :-) However seems like some fs
> inconsistency present, did you attempt rollback/finalizeUpgrade and check?
>
>  For that error, FSImage.java/code finds a previous fs state -
>
> // Upgrade is allowed only if there are
>
> // no previous fs states in any of the directories
>
> for (Iterator it = storage.dirIterator();
> it.hasNext();) {
>
>   StorageDirectory sd = it.next();
>
>   if (sd.getPreviousDir().exists())
>
> throw new InconsistentFSStateException(sd.getRoot(),
>
> "previous fs state should not exist during upgrade. "
>
> + "Finalize or rollback first.");
>
> }
>
>
>  Thanks
>
> Rekha
>
>
>   From: Azuryy Yu 
> Reply-To: "user@hadoop.apache.org" 
> Date: Thursday 21 November 2013 5:19 PM
> To: "user@hadoop.apache.org" 
> Cc: "hdfs-...@hadoop.apache.org" 
> Subject: Re: HDFS upgrade problem of fsImage
>
>   I insist hot upgrade on the test cluster because I want hot upgrade on
> the prod cluster.
>  On 2013-11-21 7:23 PM, "Joshi, Rekha"  wrote:
>
>>  Hi Azurry,
>>
>> This error occurs when FSImage finds previous fs state, and as log states 
>> you would need to either finalizeUpgrade or rollback to proceed.Below -
>>
>> bin/hadoop dfsadmin –finalizeUpgrade
>> hadoop dfsadmin –rollback
>>
>> On side note for a small test cluster on which one might suspect you are the 
>> only user, why wouldn't you insist on hot upgrade? :-)
>>
>> Thanks
>> Rekha
>>
>> Some helpful guidelines for upgrade here -
>>
>> http://wiki.apache.org/hadoop/Hadoop_Upgrade
>>
>> https://twiki.grid.iu.edu/bin/view/Storage/HadoopUpgrade
>>
>> http://hadoop.apache.org/docs/current/hadoop-project-dist/hadoop-hdfs/Federation.html#Upgrading_from_older_release_to_0.23_and_configuring_federation
>>
>>
>>   From: Azuryy Yu 
>> Reply-To: "user@hadoop.apache.org" 
>> Date: Thursday 21 November 2013 9:48 AM
>> To: "hdfs-...@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.(NameNode.java:692)
>> at
>> org.apache.hadoop.hdfs.server.namenode.NameNode.(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)
>>
>

Re: New data on unfinalized hdfs upgrade

[Harsh J]

If you "rollback", you lose all new data.

On Sat, Nov 16, 2013 at 12:25 AM, krispyjala  wrote:
> What happens if you upgrade 1.0.4 to 2.2, run some stuff that puts in new
> data while the upgrade is not finalized, but then revert back to 1.0.4? Will
> the new data also be reverted back to 1.0.4 safely?
>
>
>
> --
> View this message in context: 
> http://hadoop-common.472056.n3.nabble.com/New-data-on-unfinalized-hdfs-upgrade-tp4029496.html
> Sent from the Users mailing list archive at Nabble.com.



-- 
Harsh J