How can I install CDH 5.1.2 using Cloudera Manager?

[#1]

Hi All,

I need to emulate a Customer environment and they're using CDH 5.1.2.  I've tried a 3-node install of CDH5 using Cloudera Manager and it appears to only allow installation of 5.1.3.  Where can I find a Cloudera Manager 5.1.2 download link?  Thanks in advance for your patience and collective wisdom on this.

mit Freundlichen Grüßen (with Friendly Greetings),

     Jan

Jan Peters

[#2]

Jan,

You can find previous releases here:

http://archive-primary.cloudera.com/cm5/

If you were using RedHat, for example, you could go to:

http://archive-primary.cloudera.com/cm5/redhat/6/x86_64/cm/5.1.2/

- Ben

[#3 · Accepted solution]

Hello Jan,

If you use the Cloudera Manager "Path A" installer file (cloudera-manager-installer.bin) file on a node that already has a cloudera-manager.repo yum configuration - notably, a yum config that pointed at CM /5/ root instead of a specific version:

"http://archive-primary.cloudera.com/cm5/redhat/6/x86_64/cm/5/RPMS/x86_64/"

instead of

"http://archive-primary.cloudera.com/cm5/redhat/6/x86_64/cm/5.1.2/RPMS/x86_64/" 

... then you will end up pulling in the very latest Cloudera Manager version. This is probably what happened in your case.

Previously, when CM 5.1.2 was the latest version, the URL for /5/ pointed at /5.1.2/. Once 5.1.3 became the newest, /5/ likewise became a symlink to it.

For your purposes, and to install a version other than the very newest on a node that already has a Cloudera Manager repo configured in yum, make sure that before you run cloudera-manager-installer.bin make sure that you

# [rm/mv] /etc/yum.repos.d/cloudera-manager.repo.

By doing this, the cloudera-manager-installer.bin  for CM 5.1.2 (http://archive-primary.cloudera.com/cm5/installer/5.1.2/cloudera-manager-installer.bin) will be able to lay down its own contained Cloudera Manager repo file which will point at:

http://archive-primary.cloudera.com/cm5/installer/5.1.2/cloudera-manager-installer.bin

================

Alternatively, you could just try editing /etc/yum.repos.d/cloudera-manager.repo to change the baseurl

"http://archive-primary.cloudera.com/cm5/redhat/6/x86_64/cm/5/RPMS/x86_64/"

TO

"http://archive-primary.cloudera.com/cm5/redhat/6/x86_64/cm/5.1.2/RPMS/x86_64/" 

Let me know if this lets you proceed. Alter instructions if you're using apt-get but the concept is the same.

Or, switch to the Path B Installation method where you specifically configure your yum/apt-get repos and manually call yum install / apt-get install to specify exactly the files you want.

Regards,

--

Mark Schnegelberger

[#4]

Hi Mark,

It took a bit of mental gymnastics but I finally figured it out...  first issue for me was finding/removing artifacts from the aborted 5.1.3 install.  The install choked early on, on several artifacts and so I had to use yum --setopt=tsflags=noscripts remove <> along with yum history sync to clean up the repos.

The other big learning for me was that if I halted the install, edited the /etc/yum.repos.d/cloudera-manager.repo file and re-ran the install, CM would save out my edited version and replace it with the original one pointing to the symlink...  SO...  what I ended up doing is waiting until it was ready to install, and then edited the /etc/yum.repos.d/cloudera-manager.repo file before stepping into the install.  Additionally, the other learning was using packages rather than parcels as it allowed me to specifically select 5.1.2 among many other versions.

Thank you again for you advice and wisdom; I'll be back when I start Kerberizing this 3-node cluster.  🙂

mit Freundlichen Grüßen (with Friendly Greetings),

     Jan

Jan Peters

[#5]

Hi Mark,

Well, it seems I'm wearing egg on my face this morning...  I came back to my desk yesterday and found that all 3 nodes nuked on the install... and when I checked there was a mismatch between 5.1.3 and 5.1.2 elements. 

Seems the bin installer I pulled from http://archive-primary.cloudera.com/cm5/installer/5.1.2/cloudera-manager-installer.bin created a cloudera-manager.repo pointing at http://archive-primary.cloudera.com/cm5/redhat/6/x86_64/cm/5/RPMS/x86_64/  and even though I edited the cloudera-manager.repo to point at http://archive-primary.cloudera.com/cm5/redhat/6/x86_64/cm/5.1.2/RPMS/x86_64/   it appears it had already installed the cloudera-manager-agent-5.1.3 before I got to that point, so when it installed the rest of the manifest (the 5.1.2 elements) the entire install nuked on all 3 nodes.

So now what I've done is to yum remove everything and start over by hand...  I've now done the following;

yum install http://archive-primary.cloudera.com/cm5/redhat/6/x86_64/cm/5.1.2/RPMS/x86_64/cloudera-manager-agent-...
yum install http://archive-primary.cloudera.com/cm5/redhat/6/x86_64/cm/5.1.2/RPMS/x86_64/cloudera-manager-daemon...
yum install http://archive-primary.cloudera.com/cm5/redhat/6/x86_64/cm/5.1.2/RPMS/x86_64/cloudera-manager-server...
yum install http://archive-primary.cloudera.com/cm5/redhat/6/x86_64/cm/5.1.2/RPMS/x86_64/cloudera-manager-server...
yum install http://archive-primary.cloudera.com/cm5/redhat/6/x86_64/cm/5.1.2/RPMS/x86_64/enterprise-debuginfo-5....
yum install http://archive-primary.cloudera.com/cm5/redhat/6/x86_64/cm/5.1.2/RPMS/x86_64/jdk-6u31-linux-amd64.rp...
yum install http://archive-primary.cloudera.com/cm5/redhat/6/x86_64/cm/5.1.2/RPMS/x86_64/oracle-j2sdk1.7-1.7.0+u...

So will need to figure out how to start cloudera manager by hand to see if I can complete a very basic install with MRv1 framework and then Kerberize the cluster.  Any advice you'd have is appreciated and thanks for your patience.

mit Freundlichen Grüßen (with Friendly Greetings),

     Jan

Jan Peters