Member since
09-23-2013
238
Posts
72
Kudos Received
28
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
1845 | 08-13-2019 09:10 AM | |
3250 | 07-22-2015 08:51 AM | |
7159 | 06-29-2015 06:43 AM | |
5014 | 06-02-2015 05:17 PM | |
20984 | 05-23-2015 04:48 AM |
12-24-2014
08:59 AM
2 Kudos
Here is a screenshot of a working configuration.
... View more
12-15-2014
12:30 PM
hadoop dfsadmin -refreshNodes will help you regenerate the datanode list....
... View more
12-11-2014
04:59 AM
Rakesh, Take a look at these exiting articles on the subject of installing CM over an existing CDH cluster. It is a manual process to complete. http://community.cloudera.com/t5/forums/searchpage/tab/message?filter=labels&q=CM+existing+cluster
... View more
11-25-2014
08:26 AM
1 Kudo
In a CM managed cluster, the current runtime configs are within a current instance path (newly created each startup) in the /var/run/cloudera-scm-agent/process/###-SERVICE-roleInstance path. To identify the current one perform a ls -lrt in that path. Rollback is a function of the CM ui... You would never manually attempt rollback by manipulating anything in that path. The start/stop of the process would instantiate a new runtime config out of the SCM DB each time.
... View more
11-20-2014
09:15 PM
One follow up comment; The "host inspector" that is in the "hosts" section of the CM UI is a critical tool to be using to validate cluster configurations, it does a good job of identifying DNS/hostname/reverse lookup issues present on cluster nodes. The "loopback" (127.0.0.1) entry in /etc/hosts should only contain "localhost" references and never the host name (or fqdn) value. For reference's sake, this is discussed here: http://www.cloudera.com/content/cloudera/en/documentation/core/latest/topics/cm_ig_cm_requirements.html#cmig_topic_4_3_3_unique_1
... View more
11-17-2014
11:49 AM
The telnet context is to tell telnet (or nc, which is more common "yum install nc") to connect to the actual port you are attmpeting to access to verify TCP connectivity (telnet host.fqdn.name port) As telnet has lost favor and is no longer installed by default, netcat (nc) might be the better tool to use to verify port connectivity in the future. The telnet to its default port (23) would be expected to fail. Todd
... View more
11-17-2014
11:14 AM
1 Kudo
Did you pdate client configs with a "deploy client configurations" by any chance? I assume you are running gateway instances on the nodes things are failing from?
... View more
11-17-2014
10:40 AM
Realize that analysis of what is happening, started this morning. Given its monday AM, it will take a little bit to isolate what is going on.
... View more
11-15-2014
10:21 PM
Ok thanks, I'll report that to the engineering jira. I'll continue with this tomorrow. Something happens when downloading to the windows desktop. I'll have a ubuntu desktop online to sanity check, but it seems that anyone donwloading to mac OS desktops are fine (one of my peers in APAC tested to mac OS and it worked for him like my earlier test).
... View more
11-15-2014
01:14 PM
Just a mechanics of the testing you did question: Did you download at all from within an ubuntu desktop? Or were you dl'ing to the Windows system and then copying over to the ubuntu host? (I'm asking to shape my testing as well, I'll try a direct on ubuntu desktop). Also I'll have a quick step list for path b install using the repo direct later today on ubuntu, I'm setting that up now.
... View more