AnsweredAssumed Answered

Upgrading MapR/HBase to 2.0.0

Question asked by tc_dev on Sep 8, 2012
Latest reply on Oct 12, 2012 by nabeel
I have MapR v1.2.3 with HBase holding data that needs to be preserved.

As I am preparing to upgrade MapR to v2.0.0 I've noticed (per [this question](http://answers.mapr.com/questions/3526/missing-hadoop-ecosystem-packages-for-mapr-200)) that HBase has been separated out of the main MapR repository. In any case, the upgrade presumably would involve version change and data conversion BOTH at the MapRFS and HBase level.

The question is whether rolling upgrade is designed to properly upgrade HBase and whether this part of functionality has been sufficiently tested. If not what is the recommended procedure. Could manual upgrade be more safe, presumably if I keep a few nodes (taken offline) to keep data in old format while testing the new version on a subset of nodes?

I see a few mentions of HBase specifics in the [Manual Upgrade](http://www.mapr.com/doc/display/MapR/Manual+Upgrade) article, but nothing about it in [Rolling Upgrade](http://www.mapr.com/doc/display/MapR/Rolling+Upgrade) article. Does it mean HBase upgrade is not supported under rolling scenario or it takes care of everything automagically?

Final question is whether upgrade from lower minor version (like v1.2.3) has been tested or it is best to upgrade to the highest minor version first (v1.2.9) before jumping to v2.0.0

Outcomes