Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
3.0.0
-
None
Description
Requirements:
- ambari should drop JDK 7 support for ambari-server and ambari-managed services (infra, ams, logsearch)
- HDP 2.x should be still able to use JDK 1.7
Changes in ambari setup:
1. First the usual ambari setupChoose JDK for Ambari and Stack services: [1] Oracle JDK 1.8 + Java Cryptography Extension (JCE) Policy Files 8 [2] Oracle JDK 1.7 + Java Cryptography Extension (JCE) Policy Files 7 [3] Custom JDK
2. If JDK 7 is picked, that cannot be used for ambari (only for the stack services)
JDK 7 is detected (JDK 8 required for ambari-server), install JDK 8 as well: [1] Oracle JDK 1.8 + Java Cryptography Extension (JCE) Policy Files 8 [3] Custom JDK
The following command also can work to setup custom java_home (for stacks + ambari):
ambari-server setup -s --java-home=... --stack-java-home=...
After the commands are executed, the following properties would appear in ambari.properties
stack.java.home=/usr/jdk64/jdk1.7.0_67 stack.jdk.name=jdk-7u67linux-x64.tar.gz stack.jce.name=UnlimitedJCEPolicyJDK7.zip
During command.json generating, commandParameters would be filled with proper ambari jdk,jce info (different for infra/logsearch/ams from other services) - not hostLevelParams, as multiple command could use the same hostLevelParams (like start all services: that can start zookeeper and ams as well with the same hostLevelParams)
On ambari-upgrade, ambari process wont be able to start with jdk7 so it will be required to run ambari-server setup first (you can skip the first change jdk part, but then the user will see its needed to setup a different jdk for ambari)
In the future, it will be recommended to do the JDK upgrade before upgrading to HDP 3.0 (to avoid some issues during HDP upgrade)
Attachments
Attachments
Issue Links
- links to