Support Questions
Find answers, ask questions, and share your expertise

Cloudbreak java_home setting to jdk1.7

Explorer

Hi! On Cloudbreak1.2.1, when we fielded an ambari (2.2.1.1) cluster (HDP 2.4.0), we are getting an exported JAVA_HOME=/usr/jdk64/jdk1.7.0_67" in the docker containers--even though we have specified java 1.8 at every spot we could think of. The blueprint is based on HDP cluster running java 1.8--though I can't find the specification in the blueprint's json. Is there a Profile export that specifies the specific jdk that should be used by the containers?

Thanks!

Kenneth

1 ACCEPTED SOLUTION

Accepted Solutions

Rising Star

Hi @Kenneth Graves,

There is no cbd Profile export possiblitiy/functionality that could update the java version in the provisioned cluster's containers. Ambari docker images are built from this project. If you check the project the Ambari server and agent images created from a Centos 7 distribution and here the java version is burned in the images.

So the desired java version should be installed on the VM's Ambari containers that are provisioned by Cloudbreak.

- It could be done manually on each container and then restart them or restart the entire cluster by Cloudbreak (triggering a stop/start).

- It also could be done by defining a custom recipe that is able to install the newer java version at cluster installation on an automated way - but a new cluster should be created with the custom recipe it could not be applied on running clusters.

We have not tested jdk1.8 with our Ambari images/containers so updated the java version globally could cause other issues in some of the components that are installed by Ambari.

Br,

Tamas

View solution in original post

2 REPLIES 2

Rising Star

Hi @Kenneth Graves,

There is no cbd Profile export possiblitiy/functionality that could update the java version in the provisioned cluster's containers. Ambari docker images are built from this project. If you check the project the Ambari server and agent images created from a Centos 7 distribution and here the java version is burned in the images.

So the desired java version should be installed on the VM's Ambari containers that are provisioned by Cloudbreak.

- It could be done manually on each container and then restart them or restart the entire cluster by Cloudbreak (triggering a stop/start).

- It also could be done by defining a custom recipe that is able to install the newer java version at cluster installation on an automated way - but a new cluster should be created with the custom recipe it could not be applied on running clusters.

We have not tested jdk1.8 with our Ambari images/containers so updated the java version globally could cause other issues in some of the components that are installed by Ambari.

Br,

Tamas

View solution in original post

Explorer

Tamas,

Thanks! That was helpful.

Kenneth