2.4. Complete the Stack Upgrade

In HBASE_CONFDIR/hbase-site.xml, set the property dfs.client.read.shortcircuit to false.

In the configuration file, find the value of the hbase.tmp.dir property and make sure that the directory exists and is readable and writeable for the HBase service user and group.

chown -R $HBASE_USER:$HADOOP_GROUP $HBASE.TMP.DIR

Go to the Upgrade Folder and check in the saved global configuration file named global_<$TAG> for the value of the property hbase_pid_dir and hbase_log_dir. Make sure that the directories are readable and writeable for the HBase service user and group.

chown -R $HBASE_USER:$HADOOP_GROUP $hbase_pid_dir
chown -R $HBASE_USER:$HADOOP_GROUP $hbase_log_dir

Do this on every host where a RegionServer is installed as well as on the HBase Master host.

Check for HFiles in V1 format. HBase 0.96.0 discontinues support for HFileV1. Before the actual upgrade, run the following command to check if there are HFiles in V1 format:

hbase upgrade -check

HFileV1 was a common format prior to HBase 0.94. You may see output similar to:

Tables Processed:
                    
hdfs://localhost:41020/myHBase/.META.
hdfs://localhost:41020/myHBase/usertable
hdfs://localhost:41020/myHBase/TestTable
hdfs://localhost:41020/myHBase/t
                    
Count of HFileV1: 2
HFileV1:
hdfs://localhost:41020/myHBase/usertable/fa02dac1f38d03577bd0f7e666f12812/family/249450144068442524
hdfs://localhost:41020/myHBase/usertable/ecdd3eaee2d2fcf8184ac025555bb2af/family/249450144068442512
                    
Count of corrupted files: 1
Corrupted Files:
hdfs://localhost:41020/myHBase/usertable/fa02dac1f38d03577bd0f7e666f12812/family/1
Count of Regions with HFileV1: 2
Regions to Major Compact:
hdfs://localhost:41020/myHBase/usertable/fa02dac1f38d03577bd0f7e666f12812
hdfs://localhost:41020/myHBase/usertable/ecdd3eaee2d2fcf8184ac025555bb2af

When you run the upgrade check, if "Count of HFileV1" returns any files, start the hbase shell to use major compaction for regions that have HFileV1 format. For example in the sample output above, you must compact the fa02dac1f38d03577bd0f7e666f12812 and ecdd3eaee2d2fcf8184ac025555bb2af regions.

Upgrade HBase. You must be the HBase service user.

sudo su -l $HBASE_USER -c "hbase upgrade -execute"

Make sure that the output contains the string "Successfully completed Znode upgrade".

Use the Services view to start the HBase service. Make sure that Service Check passes.

Copy files from the backup folder /conf to /etc/oozie/conf directory.

cp {oozie-conf-bak}/oozie-site.xml /etc/oozie/conf

cp {oozie-conf-bak}/oozie-env.sh /etc/oozie/conf/oozie-env.sh

chmod -R 777 /etc/alternatives/oozie-tomcat-conf/conf

rm /usr/lib/oozie/conf

ln -s /etc/oozie/conf /usr/lib/oozie/conf

Create /usr/lib/oozie/libext-upgrade21 directory.

mkdir /usr/lib/oozie/libext-upgrade21

Copy the JDBC jar of your Oozie database to both /usr/lib/oozie/libext-upgrade21 and /usr/lib/oozie/libtools.

For example, if you are using MySQL, copy your mysql-connector-java.jar.

Copy these files to /usr/lib/oozie/libext-upgrade21 directory

cp /usr/lib/hadoop/lib/hadoop-lzo*.jar /usr/lib/oozie/libext-upgrade21

cp /usr/share/HDP-oozie/ext-2.2.zip /usr/lib/oozie/libext-upgrade21

Grant read/write access to the Oozie user.

chmod -R 777 /usr/lib/oozie/libext-upgrade21

On the Services view, make sure YARN and MapReduce2 are running.

Make sure that the Oozie service is stopped.

Upgrade Oozie. You must be the Oozie service user. On the Oozie server host:

sudo su -l {OOZIE_USER} -c"/usr/lib/oozie/bin/ooziedb.sh upgrade -run"

Make sure that the output contains the string "Oozie DB has been upgraded to Oozie version {OOZIE Build Version}.

Prepare the Oozie WAR file, run as root:

	Note
	The Oozie server must be not running for this step. If you get the message "ERROR: Stop Oozie first", it means the script still thinks it's running. Check, and if needed, remove the process id (pid) file indicated in the output.

sudo su -l {OOZIE_USER} -c "/usr/lib/oozie/bin/oozie-setup.sh prepare-war -d /usr/lib/oozie/libext-upgrade21"

Make sure that the output contains the string "New Oozie WAR file added".

Using Ambari Web UI Services > Oozie > Configs, edit the following configuration properties:

Replace the content of /usr/oozie/share in HDFS. On the Oozie server host:

Use the Services view to start the Oozie service. Make sure that ServiceCheck passes for Oozie.

Move the file to a local directory.

su -l {HCAT_USER} -c "hadoop --config /etc/hadoop/conf fs -copyToLocal /apps/webhcat/*.tar.gz ${local_backup_dir}"

Remove the old file.

su -l {HCAT_USER} -c "hadoop --config /etc/hadoop/conf fs -rm /apps/webhcat/*.tar.gz"

Copy the new file.

su -l {HCAT_USER} -c "hdfs --config /etc/hadoop/conf dfs -copyFromLocal /usr/share/HDP-webhcat/*.tar.gz /apps/webhcat/"

Move the file to a local directory.

su -l {HCAT_USER} -c "hadoop --config /etc/hadoop/conf fs -copyToLocal /apps/webhcat/hadoop-streaming*.jar ${local_backup_dir}"

Remove the old file.

su -l {HCAT_USER} -c "hadoop --config /etc/hadoop/conf fs -rm /apps/webhcat/hadoop-streaming*.jar"

Copy the new hadoop-streaming.jar file.

su -l {HCAT_USER} -c "hdfs --config /etc/hadoop/conf dfs -copyFromLocal /usr/lib/hadoop-mapreduce/hadoop-streaming*.jar /apps/webhcat"