Member since
08-29-2013
79
Posts
37
Kudos Received
20
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
7907 | 07-28-2015 12:39 PM | |
3154 | 07-22-2015 10:35 AM | |
4399 | 03-09-2015 06:45 AM | |
6200 | 10-28-2014 09:05 AM | |
15139 | 10-24-2014 11:49 AM |
03-09-2015
07:29 PM
Hi Thanks for your reply very help full.We are trying to gracefully shutdown the cluster when the UPS power is less than 20 % . That is why we need the stop command badly .Would appreciate if you could give us the exact command Sorry we are new to this
... View more
10-03-2014
09:23 AM
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-5.1.2-1.cm512.p0.116.el6.x86_64.rpm yum install http://archive-primary.cloudera.com/cm5/redhat/6/x86_64/cm/5.1.2/RPMS/x86_64/cloudera-manager-daemons-5.1.2-1.cm512.p0.116.el6.x86_64.rpm yum install http://archive-primary.cloudera.com/cm5/redhat/6/x86_64/cm/5.1.2/RPMS/x86_64/cloudera-manager-server-5.1.2-1.cm512.p0.116.el6.x86_64.rpm yum install http://archive-primary.cloudera.com/cm5/redhat/6/x86_64/cm/5.1.2/RPMS/x86_64/cloudera-manager-server-db-2-5.1.2-1.cm512.p0.116.el6.x86_64.rpm yum install http://archive-primary.cloudera.com/cm5/redhat/6/x86_64/cm/5.1.2/RPMS/x86_64/enterprise-debuginfo-5.1.2-1.cm512.p0.116.el6.x86_64.rpm yum install http://archive-primary.cloudera.com/cm5/redhat/6/x86_64/cm/5.1.2/RPMS/x86_64/jdk-6u31-linux-amd64.rpm 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+update55-2.x86_64.rpm
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
... View more
10-01-2014
01:26 AM
I've just checked the versions and yes they are different so no wonder it fails! Opsworks normally automatically installs the latest version but I'd overidden it for the upgrade testing. Thanks, John.
... View more
08-15-2014
11:38 AM
Thanks for the reply!
... View more
08-14-2014
01:43 PM
Que bueno que encontraste este thread entonces!
... View more
07-25-2014
07:37 AM
1 Kudo
Hi Greg, You found the correct way to do things, so you're already well on the way! Let's get your configuration overrides removed so th global can take precedence. Cloudera Manager will be aware that you have host-level overrides and in fact provides a way to help you batch them back to default such that they inherit this from the global setting. Here are a few screenshots of how that would look: Go to the Hosts tab, then Configuration tab. Click Monitoring on the left side and find the Cloudera Manager Agent Parcel Directory Free Space Monitoring setting you've changed. There should be grey text "Overridden by N host(s)". Expand this, then click Edit Overrides. On the overrides screen you can click the top-most checkbox to select ALL hosts for which you individually applied overrides, and tell them to revert back to inheriting their configuration from the global level: Now return to the Hosts tab, then Configuration tab. Click Monitoring on the left side and find the Cloudera Manager Agent Parcel Directory Free Space Monitoring configuration property. You'll find that in the property coulmn for this, there is no mention of overrides. All hosts are now using this global setting. Congratulations! Repeat for 'Cloudera Manager Agent Parcel Directory Free Space Monitoring Percentage Thresholds' or others as necessary. Hope this helps, -- Mark S.
... View more
07-17-2014
10:12 AM
Thanks, I was missing replacing spaces with + signs in the select statement
... View more
04-22-2014
02:48 PM
1 Kudo
Thanks - rm -rf /var/cache/yum/x86_64/6/cloudera-manager/ - yum clean all worked for me. I just downloaded the cloudera-manager-installer.bin from here.
... View more
02-28-2014
09:29 AM
Hey. Having the list of all the ports being used helped me a lot in the next problem I faced. After the deployment went fine I went back to the cloudera manager screen and the main page was not showing the graphs and statistics. There was a message saying time-out to the host. So I added the list of all the Cloudera ports to the security group and now the Cloudera manager is showing the graphs. So adding the ports into the secuirty group fixed the issue of not seeing the graphs in Cloudera manager. Any chance you know which port is responsible for graph communication ? Thanks a lot guys, Kudos !
... View more
02-26-2014
07:05 AM
1 Kudo
Hello, This page lists the supported operating systems for CDH5. There are no 32-bit OS's supported, you would need to use a 64-bit OS. This should explain the error you're seeing. CDH4 does have some limited provision for 32-bit OS's as noted in its documentation, however the 32-bit limited provisions only pertain to RHEL/Cent/SL 6.2 and not 6.5 which you report that you are using. Cloudera Manager 4 and Cloudera Manager 5 both require 64-bit OS's as well, as I believe you already noted. Regards, --
... View more
- « Previous
-
- 1
- 2
- Next »