@yashwanth Has the reply helped resolve your issue? If so, please mark the appropriate reply as the solution, as it will make it easier for others to find the answer in the future.  Thanks. ... View more

Hi @MariaZ  The error above may be a different issue . Hard to say its due to the enablement of TLS/SSL on Zookeeper. you may better raise case with the error message to troubleshoot it with logs to identify what is causing the java InterruptedException. Regards, Puneeth . ... View more

@Hadoop16 Welcome to the Cloudera Community! As this is an older post, you would have a better chance of receiving a resolution by starting a new thread. This will also be an opportunity to provide details specific to your environment that could aid others in assisting you with a more accurate answer to your question. You can link this thread as a reference in your new post. Thanks. ... View more

Hive does use stats from an external table in preparing query plan. When stats are accurate, it could estimate the size of intermediate data sets and select efficient join strategies. The only thing I noticed is the fetch task is not working. ... View more

@ehehtenandayo Has the reply helped resolve your issue? If so, please mark the appropriate reply as the solution, as it will make it easier for others to find the answer in the future. Thanks. ... View more

Hi Diana, good idea. I'll create a new thread. Thank you. ... View more

OK, thanks for the answer. It seems that the current solution can only be upgraded to the highest version of nifi that is compatible with Java8. ... View more

I don't see any error related to authorization here, is ranger authorization disabled for HMS? ... View more

@mburgess Any update from your side? ... View more

After checking the status of the underlying processes(the process for docker worker & the process which gracefully stopped docker), it was clear that all processes had been stopped. There were not any processes related to docker etc. that were running in the relevant host. Hence the "busy" state of the docker worker was false. I manually updated the state of the service in the underlying cloudera manager database and set it to "stopped" to reflect the actual status of the service similarly to the other services. After I applied that, cloudera manager reflected properly the docker daemon as stopped. Then, I was able to start the docker daemon and the whole CDSW service without any issues. The CDSW service is now fully operational and without any issues. Apparently, some hickup or glitch had prevented the update of the docker daemon state in the database that cloudera manager uses, after the daemon had been stopped. Please, let me know if that is a known bug and what may have caused the issue. Would it make sense to have a reset option for the state of the service in the UI? ... View more