Member since
04-22-2014
1218
Posts
341
Kudos Received
157
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
21863 | 03-03-2020 08:12 AM | |
12487 | 02-28-2020 10:43 AM | |
3604 | 12-16-2019 12:59 PM | |
3163 | 11-12-2019 03:28 PM | |
4956 | 11-01-2019 09:01 AM |
09-20-2016
08:41 AM
Installed Cloudera Manager packages were for RHEL6.
Uninstall cloudera-manager-agent and cloudera-manager-daemons.
Adjust yum repository in /etc/yum.repos.d/cloudera-manager.repo to EL7
Install CM agent packages, now with the correct OS version.
... View more
09-19-2016
08:10 PM
Thanks Team Yes, the issue was due to older version of ssl, had fixed this issues last. Thanks for the details shared. thank you Kashi
... View more
09-19-2016
10:53 AM
5 Kudos
HI, It is likely that the Spark client configuration is not found on this host. Try doing the following: in Cloudera Manager, go to Spark --> Instances --> Add Role Instances. Add a Gateway to this host In Cloudera Manager, go to the Spark service and click the "Actions" menu; choose "Deploy Client Configuration" Test spark-shell Based on the error, I think that spark-shell is not able to find an updated version of the client configuration. If you already have a Gateway, then I'd deploy client configuration and see if that helps. Regards, Ben
... View more
09-14-2016
12:36 PM
Hello, Gateway is a particular type of role, and it means that is a host that will receive a client configuration. So it's not a service with a process, this is the reason why is gray. Regards
... View more
09-02-2016
01:08 PM
Thank you Ben... It is my bad that i've mentioned a wrong CDH version. The actual version is CDH 5.7.0 I've opened a new topic, link as follows https://community.cloudera.com/t5/Cloudera-Manager-Installation/NAVIGATORMETASERVER-SCM-HEALTH-has-become-bad/m-p/44680#U44680 Also i've copy pasted the log from the following path : Cloudera manager -> mgmt -> quick links -> Alert
... View more
08-26-2016
07:54 AM
Glad you solved it. You might check the /var/log/cloudera-scm-server/cloudera-scm-server.log for clues about the root cause if you are curious. -Ben
... View more
08-24-2016
11:06 AM
Joey, That sounds great. I encourage you to consider going to Cloudera Manager 5.8.x so that you can leverage the new Hive Incremental Replication feature. Check it out here: http://www.cloudera.com/documentation/enterprise/latest/topics/cm_bdr_hive_replication.html#concept_tzh_dwq_fw Cheers, Ben
... View more
08-24-2016
10:33 AM
Thank you. I guess I haven't visited that URL in a while so I mis-attributed it to the upgrade.
... View more
08-08-2016
08:35 AM
1 Kudo
It works !! I find the workaround. After read again the log, I find weird the python error. So I would like to check again this error. The user zookeeper have the uid 167 and gid 153. I change the gid to 167 in /etc/passwd and /etc/group, and the db test works now !! I can now continue the setup. But I don't know why the setup wasn't good... Maybe a bug in Redhat package for the 5.7.1 version. I don't know. But finally, it works, I finish my setup and my cluster is now live ! Now I'g going to configure and optimize the configuration ! Maybe the post can help somebody. Regards,
... View more
07-26-2016
09:07 AM
2 Kudos
Hello, In short, you can stop Reports Manager and then safely remove any fsimage.tmp file. Reports Manager will download the fsimage to a temp file, index it, then rename the fsimage.tmp to fsimage. If you have fsimage files lying around or directories named after HDFS that no longer exists, they can be removed. The fact that there are fsimage.tmp files left around indicates that indexing did not complete for those files. If an HDFS service is removed, Reports Manager does not clean up the previous files automatically. By default, every hour the fsimage will be downloaded from your NameNode and indexed. If indexing is taking longer than an hour, then you can increase the interval in the Cloudera Management Service Reports Manager "Reports Manager Update Frequency" configuration. If you have specific questions about what to delete, let us know. In generaly, you should have one fsimage (or fsimage.tmp while indexing is occurring) per HDFS service that Cloudera Manager manages. If you have 2 clusters managed by Cloudera Manager, you will have two fsimage files.
... View more