Considerations for Upgrading to HBase 1.1.13

A release 6.0.x cluster installed using the MapR Installer contains an hbase.table.namespace.mappings property in the /opt/mapr/hadoop/hadoop-<version>/etc/hadoop/core-site.xml file. For example:

<property>
   <name>hbase.table.namespace.mappings</name>
   <value>*:/</value>
</property>

Release 6.0.x clusters support MapR Database, but they do not support HBase. Therefore, if you upgrade the cluster manually from Release 6.0.x, you need to remove this property in order to support HBase connections to both HBase and MapR Database.

If you do not remove the property, you might see the following message:

This client is configured to use MapR tables only. HBase status is not available. MapR cluster status  
can be viewed using the 'maprcli dashboard info' command or the UI.

Starting with EEP 6.3.0, existing HBase configuration files are automatically saved during an upgrade. This table describes what happens to HBase configuration files during an upgrade.

This example shows a listing of the configuration files that are saved after an upgrade from HBase 1.1.8 to HBase 1.1.13:

[mapr@node2 etc]$ ls /opt/mapr/hbase/
hbase-1.1.13 hbase-1.1.8.201904050941 hbaseversion

$ ls /opt/mapr/hbase/hbase-1.1.8.201904050941/conf/
hadoop-metrics2-hbase.properties hbase-env.sh hbase-policy.xml hbase-site.xml log4j.properties regionservers 
warden.hbaserest.conf warden.hbaserest.conf.template warden.hbasethrift.conf warden.hbasethrift.conf.template

Existing HBase applications might need to be modified to work properly with HBase 1.1.13 in a secure MapR cluster:

HBase API Client	No changes
HBase REST	No changes if the old client used PAM (can now be changed to mapr-sasl header)
HBase Thrift over HTTP	No change if the old client used PAM (can now be changed to mapr-sasl header)
HBase Thrift over Socket	No changes