Manual rollback Rollback Cloudera Manager to Ambari 2.7.5 Stop all services in Cloudera Manager Restore old stack symlinks on Agent nodes: hdp-select set all 3.1.5.0-152 Start Ambari Restore old configuration symlinksRestore old /etc configuration symlinks.KerberosYou must restore krb5.conf, regenerate keytabs, and check Ranger and Oozie HA mode.ZooKeeperUse the following step to restore the backed-up data for ZooKeeper. For zookeeper, the default folder is /hadoop/zookeeper.Ambari Infra SolrUse the following steps to restore backed-up ambari infras solr data. RangerRollback procedure of Ranger includes restoring Ranger admin database and Ranger KMS database. HDFSBefore starting the rollback procedure, make sure that all the HDFS service roles are stopped.YARNBefore starting the rollback procedure, make sure that HDFS and Zookeeper are rolled back. HBaseIf you have performed Zookeeper and HDFS rollback already, there are no additional rollback steps required for HBase.KafkaTo roll back Kafka, perform the following steps. AtlasPerform the following steps to restore HBase tables and ATLAS_ENTITY_AUDIT_EVENTS table. HiveBefore starting the rollback procedure, make sure that HDFS and Zookeeper have already rolled back.SparkKnow more about the Spark roll back. Oozie To roll back the Oozie service, you must restore the Oozie database. If the cluster is kerberized and Oozie is in HA mode then you must manually regenerate the oozie.ha.keytab if you have not already done so.KnoxWith the backup and rollback of Ambari, Knox is also backed up and rolled back by default.ZeppelinWith the backup and rollback of HDFS, Zeppelin is also backed up and rolled back by default.Parent topic: Rollback HDP services 3.1.5 from CDP 7.1.x
