-
Notifications
You must be signed in to change notification settings - Fork 8
0.7.2 upgrade procedure
- Log in to a JumpBox instance using SSH:
ssh ubuntu@<JumpBoxEIP> -i <key.pem>
- Run a shell script to finish the installation:
-
with Kerberos disabled:
sudo -i curl -Sso upgrade_to_v0.7.2.sh https://s3.amazonaws.com/trustedanalytics/upgrade_to_v0.7.2.sh && sudo -i bash upgrade_to_v0.7.2.sh ```
-
with Kerberos enabled:
sudo -i curl -Sso upgrade_to_v0.7.2.sh https://s3.amazonaws.com/trustedanalytics/upgrade_to_v0.7.2.sh && sudo -i KERBEROS_ENABLED=True bash upgrade_to_v0.7.2.sh ```
- Navigate to the CDH home page (this is usually at: cdh-master-2:7180) and ensure all CDH services are reporting as healthy.
- Stop the cluster:
It should look like this when stopped:
- SSH to the Cloudera Manager node (cdh-master-2).
- Delete Kafka CSD:
sudo rm /opt/cloudera/csd/KAFKA-1.2.0.jar
- Stop Cloudera Manager services:
sudo service cloudera-scm-server stop
sudo service cloudera-scm-server-db fast_stop
sudo service cloudera-scm-agent stop
- Update krb5kdc - Only for clusters with Kerberos enabled
sudo service krb5kdc stop
wget http://krb5jwt.s3-website-us-east-1.amazonaws.com/kerberos-jwt-1.3.zip
sudo unzip -od / kerberos-jwt-1.3.zip
sudo service krb5kdc start
- Upgrade Cloudera Manager.
-
Change the Cloudera Manager repository path:
sudo sed -i.bak "s/5.5.1/5.7.1/g" /etc/yum.repos.d/cloudera-manager.repo ```
-
Upgrade packages:
sudo yum clean all sudo yum upgrade cloudera-manager-server cloudera-manager-daemons cloudera-manager-agent sudo service cloudera-scm-server-db start sudo service cloudera-scm-server start sudo service cloudera-scm-agent start ```
-
Wait 1-2 minutes for Cloudera Manager to start listening on port 7180.
-
Navigate to the CDH home page and update Cloudera Manager Agents:
Private key file for the next step can be found on JumpBox. Path to the file:
/root/.ssh/id_rsa
. -
For the next wizard, you do not need to change anything.
-
After updating, the services in the cluster should look like this:
-
Click
and
. Add the new parcel url
http://archive.cloudera.com/cdh5/parcels/5.7.1/
in the configuration window: -
Click again on
and update the HGM parcel to version
1.3
:
- Upgrade the cluster:
- View of cluster upgraded to version
5.7.1
:
- It would be good to remove old CDH 5.5.1 parcels from hosts, then delete them using the CDH webUI interface.
If you cannot create organization or users, auth-gateway is having issues with znode connection. This procedure will synchronize organization and repair the problem.
cf se auth-gateway ENGINE_TIMEOUT 6000
cf restage auth-gateway
curl -X PUT -H "Authorization: $(cf oauth-token |grep bearer)" -v auth-gateway.<tap_domain>/synchronize?async=true -f
wait ~45 minutes.
curl -X PUT -H "Authorization: $(cf oauth-token |grep bearer)" -v auth-gateway.<tap_domain>/jobs/<jobId from synchronize output>