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 | |
3153 | 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 |
11-06-2020
06:30 AM
1 Kudo
@shravani CM server restart required. systemctl restart cloudera-scm-server
... View more
07-23-2019
09:36 AM
@wsmolak, This thread covers a different issue that is quite old. Let's continue the conversation in the other thread you opened if that is ok: https://community.cloudera.com/t5/Cloudera-Manager-Installation/Problem-with-path-to-parcels/m-p/93062#M17196?eid=1&aid=1 Please explain what problem you are facing if there is one.
... View more
05-03-2019
04:29 PM
Thank you gzigldrum Ill follow the same below.Appreciate your time here! Regards Yasmeen
... View more
10-19-2017
02:24 AM
in /etc/hosts for all nodes: put ip_adress FQDN DN 10.10.1.230 name.domain.com name the FQDN must be before the name
... View more
01-25-2017
12:03 PM
You can search for 'heap size' in Service Monitor and Host Monitor's configuration page. Make sure they are restarted after you save your configuration changes.
... View more
02-17-2016
12:34 PM
1 Kudo
@Spyros P. - just bringing this to closure:
With the release of Cloudera Manager 5.5.0+, the feature you asked about is now available.
http://www.cloudera.com/documentation/enterprise/latest/topics/cm_rn_new_changed_features.html#concept_z5m_1pt_nt_unique_2
"Suppression of notifications - You can suppress the warnings that Cloudera Manager issues when a configuration value is outside the recommended range or is invalid. See Suppressing Configuration and Parameter Validation Warnings. - You can suppress health test warnings. See Suppressing Health Test Results. - Suppression can be useful if a warning does not apply to your deployment and you no longer want to see the notification. Suppressed warnings are still retained by Cloudera Manager, and you can unsuppress the warnings at any time."
Hope this helps,
--
Mark
... View more
09-07-2015
07:20 AM
2 Kudos
Hi changed the location of these two directories (after looking for other things to delete to clear up my 98% disk usage). Re-started the Cloudera Manager. Checked that new directories are created in the new location (it was) and then just removed the /var/lib/cloudera-[host|service]-monitor directories. The result was amazing: [root]# df -kh Filesystem Size Used Avail Use% Mounted on /dev/sda1 19G 8.0G 9.9G 45% / Cheers Steve
... View more
07-22-2015
10:35 AM
1 Kudo
Hello TS, MySQL is a perfectly great choice to be the metadata store for the entities you mention. CM doesn't have a "default RDBMS" per se, but certain installation methods can pull postgres in for you. It's perfectly fine to elect to use MySQL instead, and I'd encourage it (as well as guiding you toward our documentation which you can cite to your firm showing that it's fine to use [1]). RDBMS choice aside, the most important consideration is making sure that you have planned for and allocated sufficient space (or the ability to easily grow the available space) for the entities that will use the RDBMS. That's the absolute key. Some people love PostgresQL, others are very savvy with MySQL. Yet others may have a mandate to use Oracle 11g in an environment. Great - Cloudera Manager and CDH support any of these options! As for your questions: <Q1> How often CM talks to its backend metadata store? A1 - Cloudera Manager remains in constant contact with its metadata store. <Q2> Is it possible to quantify the amount of data traffic from the data store to the apps? A2 - I've not done this recently, but it would be an interesting exercise. Moreso than just the Cloudera Manager Server though, a few other of the Cloudera Management Services use an RDBMS (which may be considered for placement on the same instance as the one CM uses). <Q3> Should (or must) the database exist into the same server as CM?? (In my view YES, but I am looking for strong justifications!!!) A3 - The database instance is not required to be located on the same node as Cloudera Manager Server, but if that's what makes sense in your deployment then it's fine to do so. Opting for a colocated database can, in some cases, remove network latency from the picture. But, if you have access to a dedicated database admin team that can deploy MySQL and manage it (while also making sure it is backed by reliable and fast storage), then it can also make more sense to use that rather than a non-dedicated disk that's local to the Cloudera Manager Server. Your circumstances will dictate what's best. Refer to the document 'Storage Space Planning for Cloudera Manager', as it will also help you take note of the various services that use an RDBMS and some of the considerations you should take before deployment of same. Regards, -- Mark S. [1] - http://www.cloudera.com/content/cloudera/en/documentation/core/latest/topics/cm_ig_cm_requirements.html#cmig_topic_4_4_unique_1
... View more
06-04-2015
07:57 AM
I'm in the same boat. I have 512 GB of space provisioned per machine
... View more
03-10-2015
06:10 AM
hey smark , i am having Matthew's same problem but his fix didn't work with me when i tried service cloudera-scm-server-db start the output was : Creating DB navms for role NAVIGATORMETASERVER waiting for server to start.... done server started psql: could not connect to server: Connection timed out Is the server running on host "localhost" and accepting TCP/IP connections on port 7432? waiting for server to shut down..... done server stopped Unable to create database role navms, giving up waiting for server to start..... done server started its status : pg_ctl: server is running (PID: 3808) /usr/bin/postgres "-D" "/var/lib/cloudera-scm-server-db/data" but when i tried to turn the server on : service cloudera-scm-server start it says server running [ok] but when i get its status after a while i found it dead service cloudera-scm-server status cloudera-scm-server dead but pid file exists My log error is same as the above
... View more