Home | About | Sematext search-lucene.com search-hadoop.com
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB
 Search Hadoop and all its subprojects:

Switch to Plain View
Hadoop >> mail # user >> Upgrading namenode/secondary node hardware


+
MilleBii 2011-06-14, 21:01
+
Steve Loughran 2011-06-15, 10:18
+
MilleBii 2011-06-15, 14:54
+
MilleBii 2011-06-15, 14:55
+
Steve Loughran 2011-06-16, 11:49
+
MilleBii 2011-06-16, 13:19
+
Steve Loughran 2011-06-17, 09:30
+
MilleBii 2011-06-17, 13:48
Copy link to this message
-
Re: Upgrading namenode/secondary node hardware

On Jun 15, 2011, at 3:18 AM, Steve Loughran wrote:
> yes, put it in the same place on your HA storage and you may not even need to reconfigure it. If you didn't shut down the filesystem cleanly, you'll need to replay the edit logs.
As a sidenote...

Lots of weird incompatibilities have snuck into the code with the editslog between versions.  You REALLY REALLY REALLY don't want to let editslog get processed by a different version.

Shutdown the NN, DNs, etc.  Then start the NN up to let it process the editslog.  Then shutdown the NN again with a clean editslog and do the upgrade.
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB