Fresh Cloudera Manager 4.7.2 brought Java 1.7 to our cluster and replaced Java 1.6. It's a pain

sergey.sheypak566881637 — Fri, 16 Sep 2022 08:48:58 GMT

Hi, we did upgrade Cloudera Manager from 4.6.3 to 4.7.2 on our UAT env. And Cloudera Manager did completely remove Java 1.6 and palced Java 1.7We are using Java 1.6.x and we don't want 1.7 because our Storm online procissing in not fully tested with java 1.7

Is there any possibility to forbid Cloudera Manager to install Java 1.7 and use existing one: 1.6.x?

Re: Fresh Cloudera Manager 4.7.2 brought Java 1.7 to our cluster and replaced Java 1.6. It's a pain

Grizzly — Wed, 16 Oct 2013 20:08:32 GMT

Per e-mail thread discussion 1.7 JDK was manually added before cluster upgrade, and was present within custom local yum repo at the site.

CM/CDH will pick the later JDK present to use. Per Phillp L:

Yes. We ask yum to install jdk and if yum decides that it's appropriate to install a newer version of jdk than is already installed, that is what it will do.

If you want to keep a package on a particular version, even if a newer version is available in a repo, there is a way to make yum do that:

http://blog.serverbuddies.com/how-can-i-get-yum-to-keep-package-at-a-certain-version/

question Fresh Cloudera Manager 4.7.2 brought Java 1.7 to our cluster and replaced Java 1.6. It's a pain in Archives of Support Questions (Read Only)

Fresh Cloudera Manager 4.7.2 brought Java 1.7 to our cluster and replaced Java 1.6. It's a pain

Re: Fresh Cloudera Manager 4.7.2 brought Java 1.7 to our cluster and replaced Java 1.6. It's a pain