Member since
04-22-2014
1218
Posts
341
Kudos Received
157
Solutions
My Accepted Solutions
| Title | Views | Posted |
|---|---|---|
| 26246 | 03-03-2020 08:12 AM | |
| 16387 | 02-28-2020 10:43 AM | |
| 4712 | 12-16-2019 12:59 PM | |
| 4472 | 11-12-2019 03:28 PM | |
| 6656 | 11-01-2019 09:01 AM |
08-24-2017
01:40 PM
The amount of memory to assign to the JVM is relative to the number of documents in solr core nav_elements as per the documentation. See role log to get this number from your instance. The JVM sizing formula is number of nav_elements * 200, which gives you a rough estimate of what is required for normal operation.
... View more
08-08-2017
11:22 AM
Hi @VFTR, Since the issue you are having is that the services cannot access the truststore specified that the Management Service roles use to trust the signer of Cloudera Manager's certificate, Make sure you are changing the right password. Cloudera Manager --> Clusters --> Cloudera Management Service --> Configuration Search for Cloudera Manager Server TLS/SSL Certificate Trust Store Password If you can't figure out the password, it is also OK to leave the password field blank. If the password is specified, it is required to be correct, but the services don't need to know the password to get what they need from the file. Click the blue arrow next to Cloudera Manager Server TLS/SSL Certificate Trust Store Password to revert to the default 'null' value. Save and restart the Management Service. -Ben
... View more
07-26-2017
03:22 PM
Hi @MikeJones, I'm not sure what you are saying. Either you have Kerberos authentication enabled in a cluster or you don't. In order to use BDR HDFS replication, you need to have Kerberos enabled on both clusters or not enabled in both clusters. For information about how BDR replication supports replicating between clusters in different realms, see: https://www.cloudera.com/documentation/enterprise/latest/topics/cm_bdr_replication_and_kerberos.html -Ben
... View more
07-09-2017
09:11 AM
@Yoavb, Based on the stack, the user running the process does not have permission to bind to port 514 since it is a privileged port. Try using a port higher than 1024. Also web search for "privileged ports" for some background info if needed. Ben
... View more
07-06-2017
07:31 AM
That is correct.
... View more
06-26-2017
05:07 PM
well... I resolved this by adding : -aes256-cts-hmac-sha1-96 -aes128-cts only those 2... hope this help!
... View more
06-13-2017
06:24 PM
Problem resolved with your above update.
... View more
06-02-2017
07:23 AM
Thanks a lot. I have encountered the same problem while upgrading from CDH5.10.0 to CDH5.11.0. Management services (including Navigator) where not able to start. I have followed your instructions and after restart of cloudera agent, the mgmt services were able to start.
... View more
04-20-2017
09:48 AM
At my host that i'm running the Cloudera Manager Server he bring's up this port: [root@notebook etc]# netstat -putan Conexões Internet Ativas (servidores e estabelecidas) Proto Recv-Q Send-Q Endereço Local Endereço Remoto Estado PID/Program name tcp 0 0 0.0.0.0:7180 0.0.0.0:* OUÇA 3428/java tcp 0 0 0.0.0.0:7182 0.0.0.0:* OUÇA 3428/java And then when i run a container to bind the 7182 port it refuses, because this port it's already been in use and i didnt install the agent on this host.
... View more
04-06-2017
10:48 AM
1 Kudo
@Vitali1, If you have "Dump Heap When Out of Memory" enabled, a heap dump will be generated if the process runs out of heap. The files generated can be deleted as they are only for debugging purposes. Navigator does not require them. That said, you can if you are running out of heap, increasing the heap size is likely a good first try to resolve that issue. -Ben
... View more