External co-processors are not automatically upgraded, you must upgrade them manually. Before upgrading, ensure that your co-processors are compatible with the upgrade.
There are two ways to handle co-processor upgrade:
Attempting to upgrade without upgrading the co-processor jars can result in
unpredictable behaviour such as HBase role start failure, HBase role crashing, or
even data corruption.
-
Download and distribute parcels for target version of CDP Private Cloud Base.
If the downloaded parcel version is higher than the current Cloudera Manager
version, the following error message displayed:
Error for parcel CDH-7.X.parcel : Parcel version 7.X is not
supported by this version of Cloudera Manager. Upgrade Cloudera Manager
to at least 7.X before using this version of the
parcel.
You can safely ignore this error message.
-
Run the
hbase pre-upgrade validate-cp commands to check that
your co-processors are compatible with the upgrade.
Use the CDP Private Cloud Base parcel for this step. Cloudera recommends to run the
command on an HMaster host.
For example, you can check for co-processor compatibility on
master:
$ /opt/cloudera/parcels/CDH/bin/hbase pre-upgrade validate-cp -jar /opt/cloudera/parcels/CDH/jars/ -config
Or, you can validate every table level co-processors where the table name
matches to the
.* regular
expression:
$ /opt/cloudera/parcels/CDH/bin/hbase pre-upgrade validate-cp -table .*
-
Check the Yes, I have manually upgraded the HBase co-processor
classes upgrade checkbox.
Continue the upgrade using the Cloudera Manager upgrade wizard.
