Member since
01-05-2015
235
Posts
19
Kudos Received
13
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
1856 | 01-16-2019 04:11 PM | |
4666 | 01-16-2019 01:35 PM | |
2735 | 01-16-2019 07:36 AM | |
18784 | 11-19-2018 08:08 AM | |
3137 | 10-26-2018 04:17 PM |
03-07-2018
07:15 AM
1 Kudo
Hello, Yes, that is normal. A number of these services have moved towards local file storage mechanisms based on one of a number of different storage formats such as leveldb. Most of these service no longer require an external or embeded database.
... View more
03-06-2018
12:24 PM
Hello, There may be any number of reasons why the system appears to be resolving the hostnames differently. One of the main factors which can affect how DNS resolution occurs on a system is the content of /etc/nsswitch.conf on network enabled calls. Under normal conditions the order listed in this configuration file would be files and then dns but some integration tools or patterns like the use of sssd may alter the ordering of lookups. If you would like to see what the agent is attempting to report to the Host Monitor service you may use the DnsTest class built directly into the agent code, in addition to any python based test. To do this you can use a command similar to the one shown below though you will need to alter the final file naming class path to match your agent version. Note that the output is formated in JSON. [root@master-1 ~]# /usr/java/jdk1.7.0_67-cloudera/bin/java -classpath /usr/share/cmf/lib/agent-5.12.0.jar com.cloudera.cmon.agent.DnsTest {"status": "0", "ip": "192.0.2.2", "hostname": "master-1.example.com", "canonicalname": "master-1.example.com", "localhostDuration": "10", "canonicalnameDuration": "1" }
... View more
03-06-2018
12:00 PM
Hello, I believe that in most current releases if this is a new installation we do not automatically setup the Activity Monitor Role. This role was originally used by Cloudera Management Services in conjunction with MRv1. If you are not using MRv1 and the Activity Monitor role is not visible in the list of Cloudera Management services then this is the likely reason you have not been prompted to setup and configure the external database for this service in the deployment wizards. You can check what role instances you have setup by going to: Cloudera Management Services -> Instances
... View more
04-17-2017
12:12 PM
Hello Brian, CDH 5.10 does not support JDK release versions below 1.7.x. Your JAVA_HOME must not point to jdk1.6.0_31. As this JDK is not supported by the platform I would recommend that you remove this JDK from all host in your environment as an inital troubleshooting step. You can also set environment variables like the Java Home in your global profiles, agent defaults, etc. However I would recommend removing the old JDK first. https://www.cloudera.com/documentation/enterprise/release-notes/topics/rn_consolidated_pcm.html#pcm_jdk
... View more
03-31-2017
08:01 AM
2 Kudos
Hello, Thank you for reaching out to us, in order to assist you we would need to see additional log information from Cloudera Manager. The error you have referenced indicates that no host have been added to the cluster you are attempting to install parcels to. Based on what is here at this moment this does not appear to be a bug or a change in our software behavior. In addition to that the error you provided has a differeing cluster name than the ones you provided in your screenshots. We also note that your screenshots show 'Cluster 1' as having CDH 5.0.0 deployed via packages and not via parcels. The All Host page does not show us which host are presently assigned to a specific cluster without filtering. If you have added host to Cluster 1 or another cluster please use the 'Cluster' filter on the side of the All Host page so that we can see which host are assigned to that cluster. Please confirm the cluster name, CDH release, Packaging method, and any previous deployment steps you have taken.
... View more
03-30-2017
09:22 AM
Hello, Based on what you have described it is likely that you may have encountered a bug which has been identified and corrected. Under certain conditions the package upgrade can overwrite the db.properties file located in /etc/cloudera-scm-server/. This generally occurs if you are using an external database but you still have the cloudera-scm-server-db package installed. You should not have this package installed if your database is non-local and not embedded. In order to restore service you should do the following. 1.) Stop Cloudera Manager. 2.) Inspect the contents of /etc/cloudera-scm-server 3.) Look for a backup of the db.properties file and restore it. There should be one. 4.) If there is no backup alter the existing properties to point to the correct database.
... View more
03-24-2017
08:59 AM
Hello, Thank you for reaching out to us on this, unfortunately at this time we do not provide any easily configurable mechanisms to make TLS on the backing databases simplistic to deploy. Generally speaking the JDBC drivers that allow these applications to talk to the database are capable of handling TLS but they must be configured by hand or through safety valves depending on the specific service. If you are a licensed customer please contact your Account Team for assistance.
... View more
03-16-2017
01:00 PM
Hello, Our engineering teams have confirmed the conditions you have identified. We expect corrections to be availble in future releases.
... View more
03-15-2017
10:20 AM
Hello Cindy, An external database is one that is not on the same host as Cloudera Manager. We check additional parameters in our code to verify that the database is in fact non-local or not the embeded ones we install through deployment Path A. I included the conditions we presently look for in that response to you previously. Database migrations are complex, if you want to avoid this problem altogether you should follow deployment Path B especially for production environments where you will need to setup the RDBMS on your own externally. Selecting external database and pointing at the same local database istances will not make your database an external one. The scm_prepare scripts you are pointing at take a variety of options. External databases will generally not use localhost because they are RDBM systems located on another host. Generally speaking placing your database structures on application servers can be bad outside of POC conditions. If you are a licensed customer and need help please open a case with us.
... View more
03-14-2017
11:22 AM
Hi, Thank you for the information you have provided. I have created an internal case to investigate this. If we have any additional questions we weill attempt to reach out to you directly. If you are a licensed customer you may also submit a case or contact a member of your account team.
... View more
- « Previous
- Next »