Member since
09-25-2015
53
Posts
32
Kudos Received
4
Solutions
My Accepted Solutions
| Title | Views | Posted |
|---|---|---|
| 2518 | 04-06-2017 07:10 PM | |
| 8131 | 08-24-2016 06:55 PM | |
| 5984 | 12-16-2015 03:44 PM | |
| 7143 | 12-08-2015 12:54 PM |
01-26-2026
07:41 AM
Summary If you have lost your RMON db password and need to retrieve it, in CM GUI it is **** out. This article will tell you have you can retrieve it in plain text. Symptoms Any customer needing to get into RMON db but not having the password would need to get the password to get in (assuming they do not have DB ROOT) Instructions To retrieve the password we can do an API call that gives us the RMON db config info. api/v31/cm/service/roleConfigGroups/mgmt-REPORTSMANAGER-BASE/config an example would be: curl -u admin:admin GET http://ccycloud-1.oteixeira-ubuntu2004.root.comops.site:7180/api/v31/cm/service/roleConfigGroups/mgmt-REPORTSMANAGER-BASE/config
And the results would appear similar to: {
"items" : [ {
"name" : "headlamp_database_host",
"value" : "ccycloud-1.oteixeira-ubuntu2004.root.comops.site:3306"
}, {
"name" : "headlamp_database_name",
"value" : "reportsmanager9f05b8e6450d2994f37859d1ee3f1967"
}, {
"name" : "headlamp_database_password",
"value" : "reportsmanager9f"
}, {
"name" : "headlamp_database_type",
"value" : "mysql"
}, {
"name" : "headlamp_database_user",
"value" : "reportsmanager9f"
}, {
"name" : "headlamp_heapsize",
"value" : "1073741824"
}, {
"name" : "process_auto_restart",
"value" : "false"
}, {
"name" : "process_swap_memory_thresholds",
"value" : "{\"critical\":\"never\",\"warning\":\"never\"}"
} ]
}
... View more
Labels:
01-26-2026
07:36 AM
Summary Yarn distributed shell test job fails when running with Ldap group mapping turned on with basic CDP 7.1.9 SP1 cluster using Java 17 JDK. 24/12/11 15:21:29 ERROR distributedshell.ApplicationMaster: Error running ApplicationMaster java.lang.IllegalAccessError: class org.apache.hadoop.security.LdapGroupsMapping (in unnamed module @0x3901d134) cannot access class com.sun.jndi.ldap.LdapCtxFactory (in module java.naming) because module java.naming does not export com.sun.jndi.ldap to unnamed module @0x3901d134 at org.apache.hadoop.security.LdapGroupsMapping.<clinit>(LdapGroupsMapping.java:264) Symptoms Applies to New clusters using CDP 7.1.9 SP1 and Java 17 JDK with Ldap group mapping on. Instructions Need to add In Yarn - Configuration - search for yarn.nodemanager.admin-env and change the NodeManager Group (all of them if you have more then one) to: JDK_JAVA_OPTIONS=--add-opens=java.base/java.net=ALL-UNNAMED --add-opens=java.base/java.util=ALL-UNNAMED --add-opens=java.base/java.util.concurrent.atomic=ALL-UNNAMED --add-opens=java.base/java.util.regex=ALL-UNNAMED --add-opens=java.base/java.lang=ALL-UNNAMED --add-opens=java.base/java.time=ALL-UNNAMED --add-opens=java.base/java.io=ALL-UNNAMED --add-opens=java.base/java.nio=ALL-UNNAMED --add-exports=java.base/sun.net.dns=ALL-UNNAMED --add-exports=java.base/sun.net.util=ALL-UNNAMED --add-exports=java.naming/com.sun.jndi.ldap=ALL-UNNAMED --add-opens=java.naming/com.sun.jndi.ldap=ALL-UNNAMED --add-opens=java.base/java.lang=ALL-UNNAMED --add-exports=java.base/sun.net.dns=ALL-UNNAMED --add-exports=java.base/sun.net.util=ALL-UNNAMED,MALLOC_ARENA_MAX=$MALLOC_ARENA_MAX
... View more
10-22-2025
01:12 PM
Summary If you are using Java Garbage collection arguments in your settings, when you move to Java 11 or 17 from Java 8 or prior, the settings have changed. Applies to Anyone who has moved to Java 11 or 17 and requires GC logging. Instructions In the old GC (Java 8 and prior) logging settings, you would use something similar to: -Xloggc:/var/log/cloudera-scm-server/gc.log
-XX:+PrintGCDetails
-XX:+PrintGCTimeStamps
-XX:+PrintGCDateStamps In Java 11 and 17 this will actually cause an error as these are no longer used. To get similar output we recommend: -Xlog:gc*,time:file=/var/log/cloudera-scm-server/gc-%t.log where gc* will log anything related to GC up to INFO level time will give the equivilant data that used to be PrintGCTimeStamps and PrintGCDateStamps file will allow you to set an output file and it's location %t gives you a date stamp in the file name on creation (ex. gc-2025-05-23_11-56-54.log)
... View more
07-23-2024
06:44 AM
Cloudera Manager also has a great way to set class level debug on the fly without restart when needed to troubleshoot. The way to do this is to navigate to: http://<cm-server>:7180/cmf/debug/logLevel Once at this page, chose the class you wish to change, choose the radio button for the level that you wish to change it to, and hit the submit button. Understand that these changes will NOT persist a restart of the server but will start logging at the new level as soon as you hit the submit button on the logLevel page.
... View more
07-23-2024
06:33 AM
The JDK 8 HotSpot JVM is now using native memory for the representation of class metadata and is called Metaspace. The permanent generation has been removed. The PermSize and MaxPermSize are ignored and a warning is issued if they are present on the command line.
... View more
05-05-2017
01:15 PM
All, This is actually a BUG, as ambari removes the falcon service but not the hooks in Oozie configs. The proper way to fix this and not have it hit you each time you upgrade is to remove the below listed values from your oozie configs. I have also opened an internal (to Hortonworks) JIRA to have this fixed in future versions of Ambari. oozie.service.ProxyUserService.proxyuser.falcon.hosts
oozie.service.ProxyUserService.proxyuser.falcon.groups
oozie.service.URIHandlerService.uri.handlers
oozie.services.ext
oozie.service.ELService.ext.functions.coord-job-submit-instances
oozie.service.ELService.ext.functions.coord-action-create-inst
oozie.service.ELService.ext.functions.coord-action-create
oozie.service.ELService.ext.functions.coord-job-submit-data
oozie.service.ELService.ext.functions.coord-action-start
oozie.service.ELService.ext.functions.coord-sla-submit
oozie.service.ELService.ext.functions.coord-sla-create
... View more
04-06-2017
07:10 PM
1 Kudo
While we do not provide a best practice to this I suggest the following:
1. Bring down the entire cluster cleanly and perform the RAM upgrade. 2. Use this to determine what all your new config settings should be:
http://docs.hortonworks.com/HDPDocuments/HDP2/HDP-2.6.0/bk_command-line-installation/content/determine-hdp-memory-config.html (or use the correct one for your HDP release, this is from 2.6.0) 3. Once you change your memory settings, restart the cluster.
... View more
03-21-2017
03:58 PM
2 Kudos
In the past, if Select returned no rows, hadoop would still create an empty file. Some customer would use this file to help with their work flow. In https://issues.apache.org/jira/browse/HIVE-13040 this was fixed, because anyone using cloud based solutions could be charged for empty files, so it was determined that hadoop should not write the files.
... View more
Labels:
01-12-2017
07:39 PM
3 Kudos
I can confirm for you that the deletes look correct. I normally do not do the alters, but I don't see them causing an issue. Remember to STOP ambari-server before editing. Take a good backup of the db. Then when done, start ambari-server.
... View more
08-24-2016
07:42 PM
@Arun A K I just use the Web Gui that comes with IPA ldap. Keep in mind I am not managing a large user base, but rather just doing small recreations to help customers. I would think the GUI would get cumbersome if you were doing an entire enterprise.
... View more