@RickWang If you can point the exact repo on GitHub I can try to take a look and can come with an answer. Normally if this is available on public Git then you can fork and modified as per convenience in my opinion. ... View more

@Phantom No CDH4 is discontinued and not on internet as well. If you have old Internal Repository setup then you can try to install but from internet it's not possible.    One way I can think of is try to manually place the parcels on the new node but again you might not have agent version so it will be a mess. If you are having a paid subscription then I would suggest you to upgrade to some supported version or AT LEAST publicly available version and then add node.    Without Subscription New Node Addition is not possible.  ... 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

@nanc Ideally None of them is required. However if needed only CM server Restart can take care of the license.  ... View more

@MajidAli Have you tried restarting the CM server and look at the CM server logs to see the full error?  Log can be found under /var/log/cloudera-scm-server/cloudera-scm-server.log ... 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