Hello @Raj78 ,   thank you for enquiring about how to set up Livy against CDH. Please note, Livy is supported for CDP, however it is not supported on CDH6. The main reason of a product not being supported in a certain version is that it is not production ready for those releases.   Please evaluate our CDP product.   Please find here the documentation for configuring Livy ACLs on CDP.   Please let us know if you need more information on this topic.   Best regards: Ferenc     ... View more

Hello @NumeroUnoNU ,   I've run the "alternatives --list" command on a cluster node and noticed that there is a "hadoop-conf" item, which points to a directory that has the hdfs-site.xml location.   You can also discover it by: "/usr/sbin/alternatives --display hadoop-conf".   This lead to me to google for "/var/lib/alternatives/hadoop-conf" and found this Community Article reply, which I believe answers your question.   In short if you have e.g. gateway roles deployed for HDFS on a node, you will find the up-to-date hdfs-site.xml in /etc/hadoop/conf folder...   We have a little bit diverged from the original topic in this thread. To make the conversation easier to read for future visitors, would you mind open a new thread for each major topics, please?   Please let us know if the above information helped you by pressing the "Accept as Solution" button.   Best regards: Ferenc ... View more

Hello @NumeroUnoNU ,   yes, you either parse the contents of the hdfs-site.xml or you utilise the HDFS Client, so you do not need to worry about implementation details. I've just quickly googled for you an explanation of what is HDFS Client [1]. If you go for the parsing exercise, make sure you are not referencing the NN, otherwise on failover you should prepare your script to handle that situation.   Kind regards: Ferenc   [1] https://stackoverflow.com/questions/43221993/what-does-client-exactly-mean-for-hadoop-hdfs ... View more

Hello @iceqboy ,   thank you for raising your enquiry about how to upgrade the OS version on a cluster.   As a first step, please upgrade your OS.   [1] points out that temporarily - while the OS upgrade is carried out - it is supported by Cloudera to run on mixed minor version releases. It means that it is less risky to run on different minor OS releases than on different OS-es.   [2] describes that: "Upgrading the operating system to a higher version but within the same major release is called a minor release upgrade. For example, upgrading from Redhat 6.8 to 6.9. This is a relatively simple procedure that involves properly shutting down all the components, performing the operating system upgrade, and then restarting everything in reverse order."   Once the cluster is on the same OS release, the next step is to upgrade your CM [3]. The CM version has to be higher or equal to the CDH version you are upgrading to. Then please follow our documentation on how to upgrade to CDH5.16. [4]   Please let us know if we addressed your enquiry!   Best regards: Ferenc   [1] https://docs.cloudera.com/documentation/enterprise/release-notes/topics/rn_consolidated_pcm.html [2] https://docs.cloudera.com/cdp/latest/upgrade-cdh/topics/ug_os_upgrade.html [3] https://docs.cloudera.com/cdp/latest/upgrade-cdh/topics/ug_cm_upgrade.html [4] https://docs.cloudera.com/cdp/latest/upgrade-cdh/topics/ug_cdh_upgrade.html ... View more

Hello @mhchethan ,   I have reached out to Product Management internally and the binaries for SLES12 SP1 can be used for SP3 too. Raised a jira internally, so our doc would reflect this in the future.   Please let us know if you need any further information!   Thank you: Ferenc ... View more