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 @Saimukunth ,   thank you for reaching out!    Please note, the docker image is based on CDH5.13 and no longer maintained.  You can still browse however the instructions on how to run the docker image.   Going forward, we encourage you to trial our latest product line, CDP.   Please let us know if you need any further input regarding to trialling CDP.   Best regards: Ferenc ... View more

Hello @ijarvis ,   - If you are looking to try out HDP, please consider downloading our HDP Sandbox [1]. It does not require to become a subscription customer or to have paywall credentials.   - If you would like to deploy HDP in a production environment, please reach out to our Sales Team [2] to guide you further. Once you are a subscription customer, make sure you are registered to our Support Portal [3], please. Please note, the Community Portal registration is different from the Support Portal one. After logging in to the Support Portal, you can navigate to the Downloads page and follow an automated process for the paywall credentials. You will need your license key ready to generate the paywall credential, if you need a copy of the license key, you can open a non-technical case to request it (once you are registered and logged in to our Support Portal).  The binaries are behind a paywall for which you need paywall credentials. Please see more about our Licencing Policy FAQ under [4].   - you can always download and compile the source code [5], which is not behind the paywall   Please let me know if you need further input!   Thank you: Ferenc    [1] https://www.cloudera.com/downloads/hortonworks-sandbox.html [2] https://www.cloudera.com/contact-sales.html [3] https://sso.cloudera.com/register.html [4] https://www.cloudera.com/products/faq.html [5] https://github.com/hortonworks/hadoop-release/releases ... View more

There is currently a bug.  Please try the following:   Click Parcel Repositories & Network Settings   You should see a error that looks like:   Remove that URL, and replace it with: https://archive.cloudera.com/cdh7/7.1.1.0/parcels/   This solution could be resolved or could change over time as newer versions of CM and Cloudera Runtime are released.    ... View more

Hello @Mondi ,   thank you for raising your question about why application logs being deleted from the nodes after the applications finished running and why is it happening, how to keep them in place.   When log aggregation is enabled with the 'yarn.log-aggregation-enable = true' [1] you will observe the behaviour described: after the logs are aggregated to HDFS, the logs are immediately deleted from the local file system. Log aggregation does not start until the application is finished. If you need to keep the logs and some other temporary files on the local node for troubleshooting and you have log aggregation turned on then you can use yarn.nodemanager.delete.debug-delay-sec . This is set to 0 seconds by default causing the immediate delete.   Should you disable log aggregation, non aggregated logs are kept for yarn.nodemanager.log.retain-seconds = 10800 seconds (3*3600 seconds or 3 hours). After that the NodeManager will delete the log files.   Please let us know if your enquiries been addressed!   Thank you: Ferenc   [1] https://hadoop.apache.org/docs/r2.7.0/hadoop-yarn/hadoop-yarn-common/yarn-default.xml ... View more

@Mondi    You would still need to secure your cluster since any user can be impersonated in a non kerberised cluster. Refer https://blog.cloudera.com/how-to-secure-internet-exposed-apache-hadoop/ for more details on securing your cluster. ... View more

Hello @BSST ,   this page details about memory and storage recommendations per host: https://docs.cloudera.com/cdpdc/7.0/release-guide/topics/cdpdc-hardware-requirements.html   Is it what you were looking for, please?   Thank you: Ferenc ... View more