@muslihuddin No I didn’t find any other bug. Not sure in your case by the modification of java.security file didn’t worked alone. The solution you are having atm is also fine in my opinion no harm in that.  ... View more

@wenzf Yes, you can try with that.  ... View more

@muslihuddin You are running into a known Java Bug which has been found Earlier and documented. You have to follow below steps to overcome this issue.. For JDK 8u241 and higher versions running on Kerberized clusters, you must disable referrals by settingsun.security.krb5.disableReferrals=true. For example, with OpenJDK 1.8.0u242: Open /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.242.b08-0.el7_7.x86_64/jre/lib/security/java.security with a text editor. Add sun.security.krb5.disableReferrals=true (it can be at the bottom of the file). Add this property on each node that has the impacted JDK version. Restart the applications using the JDK so the change takes effect. For more information, see the KB article. You can so many similar discussion on Cloudera Community which has been resolved Earlier.  [1] https://docs.cloudera.com/cdp-private-cloud-upgrade/latest/release-guide/topics/cdpdc-java-requirements.html   ... View more

@ebeb Are you able to kinit from the host with the existed keytab? That’s a vlid check to start with and then see where is the issue.  ... View more

@xpouser You want to take a look at : https://hadoop.apache.org/docs/stable/hadoop-yarn/hadoop-yarn-site/GracefulDecommission.html   ... View more

@noamsh_88 It’s not tested that C5.1.1 can work with upgraded log4j as this is no more under support cycle and no testing going on.  However you can give it a try but keep in mind CDH5 is not impacted with log4j vulnerability so you might have to examine first what is desired and then take action.  ... View more

No @ronys I think the installation of the worker node is corrupted somehow. This error seems related with kubeconfig file and may be you want to try delete the node again and clean that and then re add as worker.  ... View more