Skip to main content

Update Cloudera Manager

Update Cloudera Manager to specific version [5.4.5]

Take database backup.

If we are running a dedicated database which is recommended in production setup. then we need to take a backup of the DB as a precaution.
Assuming we are using a dedicated DB.

Stop Cloudera Manager Server, Database, and Agent

Shutdown cloudera manager server.
sudo service cloudera-scm-server stop
If cloudera manager is also running an Agent service. 
sudo service cloudera-scm-agent stop
NOTE : If we are using a standalone/embedded database then we need to stop that as well.
sudo service cloudera-scm-server-db stop

Update repository to get the latest rpm.

Create a file cloudera-manager.repo with below contents.
[cloudera-manager]
# Packages for Cloudera Manager, Version 5.4.5, on RedHat or CentOS 6 x86_64
name=Cloudera Manager
baseurl=http://archive.cloudera.com/cm5/redhat/6/x86_64/cm/5.4.5/
gpgkey=http://archive.cloudera.com/cm5/redhat/6/x86_64/cm/RPM-GPG-KEY-cloudera 
gpgcheck=1
copy cloudera-manager.repo to /etc/yum.repos.d/
$ sudo yum clean all
$ sudo yum upgrade cloudera-manager-server cloudera-manager-daemons cloudera-manager-agent
Check if all the installation was good.
$ rpm -qa 'cloudera-manager-*'
cloudera-manager-repository-5.0-1.noarch
cloudera-manager-server-5.4.7-0.cm544.p0.932.el6.x86_64
cloudera-manager-server-db-2-5.4.7-0.cm544.p0.932.el6.x86_64
cloudera-manager-agent-5.4.7-0.cm544.p0.932.el6.x86_64
cloudera-manager-daemons-5.4.7-0.cm544.p0.932.el6.x86_64

Start the Cloudera Manager Server (Packages)

sudo service cloudera-scm-server start
sudo service cloudera-scm-agent start

Upgrade CDH version from 5.4.2 to 5.4.5

Manually adding - Parcel to Repository

  • Download and copy parcel to /opt/cloudera/parcel-repo on cloudera Manager.
wget http://archive.cloudera.com/cdh5/parcels/5.4.5/CDH-5.4.5-1.cdh5.4.5.p0.7-el6.parcel`
  • Download the sha file and copy to /opt/cloudera/parcel-repo directory.
wget http://archive.cloudera.com/cdh5/parcels/5.4.5/CDH-5.4.5-1.cdh5.4.5.p0.7-el6.parcel.sha1
  • Change permission to both files above to cloudera-scm.
  • Rename file which has the shasum from CDH-5.4.5-1.cdh5.4.5.p0.7-el6.parcel.sha1 to CDH-5.4.5-1.cdh5.4.5.p0.7-el6.parcel.sha.
  • Now check on Cloudera Manager portal for the new parcel.
  • Here is the link to the parcel http://cloudera-manager-server:7180/cmf/parcel/status
  • It will take 5-10min to update the list of parcels. Depending on the refresh frequency.
  • Once it is does we will see a Distruibute button.
  • Click Distruibute and then Active.
  • Next go to home and click on cluster and select upgrade cluster, follow the instructions.
  • Restart the cluster. Do a Rolling restart.
  • We are done.
​
Labels:

Comments

Post a Comment

Popular posts from this blog

Cloudera Manager - Duplicate entry 'zookeeper' for key 'NAME'.

We had recently built a cluster using cloudera API’s and had all the services running on it with Kerberos enabled. Next we had a requirement to add another kafka cluster to our already exsisting cluster in cloudera manager. Since it is a quick task to get the zookeeper and kafka up and running. We decided to get this done using the cloudera manager instead of the API’s. But we faced the Duplicate entry 'zookeeper' for key 'NAME' issue as described in the bug below. https://issues.cloudera.org/browse/DISTRO-790 I have set up two clusters that share a Cloudera Manger. The first I set up with the API and created the services with capital letter names, e.g., ZOOKEEPER, HDFS, HIVE. Now, I add the second cluster using the Wizard. Add Cluster->Select Hosts->Distribute Parcels->Select base HDFS Cluster install On the next page i get SQL errros telling that the services i want to add already exist. I suspect that the check for existing service names does n
2 comments
Read more

Zabbix History Table Clean Up

Zabbix history table gets really big, and if you are in a situation where you want to clean it up. Then we can do so, using the below steps. Stop zabbix server. Take table backup - just in case. Create a temporary table. Update the temporary table with data required, upto a specific date using epoch . Move old table to a different table name. Move updated (new temporary) table to original table which needs to be cleaned-up. Drop the old table. (Optional) Restart Zabbix Since this is not offical procedure, but it has worked for me so use it at your own risk. Here is another post which will help is reducing the size of history tables - http://zabbixzone.com/zabbix/history-and-trends/ Zabbix Version : Zabbix v2.4 Make sure MySql 5.1 is set with InnoDB as innodb_file_per_table=ON Step 1 Stop the Zabbix server sudo service zabbix-server stop Script. echo "------------------------------------------" echo " 1. Stopping Zabbix Server &quo
1 comment
Read more

Access Filter in SSSD `ldap_access_filter` [SSSD Access denied / Permission denied ]

Access Filter Setup with SSSD ldap_access_filter (string) If using access_provider = ldap , this option is mandatory. It specifies an LDAP search filter criteria that must be met for the user to be granted access on this host. If access_provider = ldap and this option is not set, it will result in all users being denied access. Use access_provider = allow to change this default behaviour. Example: access_provider = ldap ldap_access_filter = memberOf=cn=allowed_user_groups,ou=Groups,dc=example,dc=com Prerequisites yum install sssd Single LDAP Group Under domain/default in /etc/sssd/sssd.conf add: access_provider = ldap ldap_access_filter = memberOf=cn=Group Name,ou=Groups,dc=example,dc=com Multiple LDAP Groups Under domain/default in /etc/sssd/sssd.conf add: access_provider = ldap ldap_access_filter = (|(memberOf=cn=System Adminstrators,ou=Groups,dc=example,dc=com)(memberOf=cn=Database Users,ou=Groups,dc=example,dc=com)) ldap_access_filter accepts standa
Post a Comment
Read more