Member since
04-22-2014
1218
Posts
341
Kudos Received
157
Solutions
My Accepted Solutions
| Title | Views | Posted |
|---|---|---|
| 26261 | 03-03-2020 08:12 AM | |
| 16421 | 02-28-2020 10:43 AM | |
| 4725 | 12-16-2019 12:59 PM | |
| 4475 | 11-12-2019 03:28 PM | |
| 6679 | 11-01-2019 09:01 AM |
08-27-2018
10:25 PM
1 Kudo
@aasf, I think it has been consollodated on this page: https://www.cloudera.com/content/dam/www/marketing/resources/datasheets/cloudera-enterprise-datasheet.pdf.landing.html#cmfeig_topic_5_1 See page 2 of the embedded doc. If you have any other questions, we are happy to assist.
... View more
08-27-2018
01:11 PM
The fix for this was to upgrade CDH from 5.5.1 to 5.13.3
... View more
08-24-2018
11:27 PM
@hadoopuser2000, Are you still having trouble? The screen shots indicate you need to uninstall before installing again, so I'd try that. I wasn't clear how the screen shots were related to the problem connecting to CM. First, make sure CM is running; # netstat -nap |grep 7180 If you see that it is listening, make sure that you can connect to the host on which Cloudera Manager is installed from whatever client you are using to connect to Cloudera Manager. By public address, the doc means that you should use whatever hostname will resolve to an IP that lets you connect to that host and port.
... View more
08-24-2018
08:56 PM
@supahcraig, I am glad you were able to resolve the problem. Usually if the upgrade stalls during distribution you can view details about which hosts have successfully downloaded the parcel via the the parcels page. Clicking the progress bar will open a page that shows the progress for each host. Once you find a host or hosts that have errors or are not completing, you can mouse over or click on the bar to view more details including the hostname. Once you have the hostname, you can ssh to that host and review the agent log there (/var/log/cloudera-scm-agent/cloudera-scm-agent.log) The agent actually downloads the parcel file so you can see information about any problems in the agent log. Here is a page that shows more about the parcels: https://www.cloudera.com/documentation/enterprise/5-9-x/topics/cm_ig_parcels.html Cheers!
... View more
08-24-2018
06:10 PM
1 Kudo
@DaveO, The exception means that the agent cannot log into the supervisor. For some reason the agent's password is not the same as the running supervisor. I wonder if this host had an agent already running when you tried to install or something like that. To correct this, check for running supervisor processes For example "ps aux |grep supervisor | grep agent" and kill them if they are any When no supervisor processes are running, try starting the agent again and see if it starts/connects to a new supervisor.
... View more
08-24-2018
05:53 PM
2 Kudos
@balaganAtomi, The link is good now. There may have been a brief issue... Let us know if it is still not working for you.
... View more
08-22-2018
11:43 PM
@vijithv, First, firewalls can easily block UDP and allow TCP. I mentioned that was a possible cause. Also, depending on how you have your /etc/krb5.conf configured, a different KDC could have been contacted. You can see distinctly in the failure via UDP that there is a socket timeout for each attempt to connect to the KDC. This is a failure at the networking side where a client cannot connect to a server. Since no connection was ever made via UDP, there was no change for it to know to try TCP. That "switching" is done based on a response of KRB5KRB_ERR_RESPONSE_TOO_BIG I believe so if no response is made, no "switching" to TCP will occur. If you really want to get to the bottom of this, recreate the problem while capturing packets via tcpdump like this: # tcpdump -i any -w ~/kerberos_broken.pcap port 88 Then, with the problem fixed reproduce again while capturing packets: # tcpdump -i any -w ~/kerberos_fixed.pcap port 88 Use Wireshark (it does a great job of decoding Kerberos packets) and you will be able to see the entire interaction. This will show us information to help determine the cause. Wireshark is here: https://www.wireshark.org/
... View more
08-22-2018
10:48 PM
1 Kudo
@sbpothineni, You can find more information regarding the Cluster Utlization Report here: https://www.cloudera.com/documentation/enterprise/latest/topics/admin_cluster_util_report.html and about Reports Manager reports here: https://www.cloudera.com/documentation/enterprise/5-15-x/topics/cm_dg_reports.html The Cluster Utilization report shows metrics regarding YARN and Impala jobs/queries The Reports from Reports Manager show information about HDFS
... View more
08-22-2018
04:57 PM
@DanielWhite, There is a Cloudera Manager command and a YARN job. - To Abort the command, you can click on the Command Details button under the replication schedule with a running command. - If the YARN job continues to run, you can kill it like any other YARN job. Aborting/Killing is safe. The next time you run replication, any files that were already copied will be skipped; any that weren't copied will be copied.
... View more
08-22-2018
12:38 PM
Thank you, Mr.bgooley for supporting me from past two posts. Your reply gave me joe. The Cloudera-scm-agent was successfully installed and the update went smoothly As you said ubuntu xenial is supporting the CDH5. Kindly give me solution for another problem what I got in the further step which is the database set up please refer the link which shows my post on the community http://community.cloudera.com/t5/Cloudera-Manager-Installation/Problem-in-database-set-up-in-cloudera-manager/m-p/78830 Thanks, solomonchinni
... View more