About AKR

AKR · ‎01-06-2020

Hi, As mentioned in the previous posts, did you tried increasing the memory and whether it solved the issue? Please let us know if you are still facing any issues? Thanks AKR

AKR · ‎01-05-2020

Hi, This seems to be a Kerberos authentication problem. is this issue happens only for a SHS2 UI or does it happens for other URLs too? You could do a1. kinit username 2. kinit -kt service.keytab 3. send keytab file along with the submit command Thanks AKR

AKR · ‎12-09-2019

Hi, If you are looking for 2.4 on HDP alone means, as mentioned in previous emails, don't expect any new HDP version anytime before the release of the combined new offering Cloudera Data Platform (CDP) sometime in 2020 or thereafter. As an alternative CDH 6.2+ supports spark 2.4 version. Thanks AK

AKR · ‎10-11-2019

Hi, Did you tried taking backup of the folder /var/lib/hadoop-yarn/yarn-nm-recovery/yarn-nm-state. and deleting all the contents under /var/lib/hadoop-yarn/yarn-nm-recovery/yarn-nm-state and restarting affected node manager? Please share the updates Thanks AKR

AKR · ‎09-05-2019

Hi, Exit code 143 is related to Memory/GC issues. Your default Mapper/reducer memory setting may not be sufficient to run the large data set. Thus, try setting up higher AM, MAP and REDUCER memory when a large yarn job is invoked. For more please refer to this link. https://stackoverflow.com/questions/42972908/container-killed-by-the-applicationmaster-exit-code-is-143 Thanks AKR

Nandyal · ‎06-12-2019

After making a small change to the location of the jar, we got it working. The steps are as follows: added the hbase jars to the executor classpath via the following setting: signed in to ClouderaManager went to the Spark on YARN service went to the Configuration tab typed defaults in the search box selected gateway in the scope added the entry: spark.executor.extraClassPath=/hdfs03/parcels/CDH/lib/hbase/lib/htrace-core-3.2.0-incubating.jar Note: we had to use the hdfs directory path.

AKR · ‎05-14-2019

Hi, The 'major.minor version 52.0' error is possibly because the jar was compiled in JDK 1.8, but you are trying to run it using a JDK 1.7 environment. The reported number is the required number, not the number you are using. To solve this, it's always better to have the JDK and JRE pointed to the same version.

Online	Offline
Last Visited	‎08-25-2026 07:16 AM

Member Since	‎09-20-2018 10:06 PM
Last Visited	‎08-25-2026 07:16 AM
Posts	366

Cloudera Community

Re: Can't start Kafka Service broker

Re: Spark job getting failed with Jupyter notebook

Re: Spark2 history server UI not opening in HDP 3....

Re: Which version of HDP supports spark 2.4

Re: Unable to start Node manager

Re: Diagnostics: Container killed on request. Exit...

Re: Caused by: java.lang.NoClassDefFoundError: org...

Re: Can't start Kafka Service broker