ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sumit Mohanty (JIRA)" <>
Subject [jira] [Commented] (AMBARI-21099) Drop JDK 7 support for Ambari Server and Ambari managed services (AMS, LogSearch, Infra)
Date Wed, 28 Jun 2017 20:58:00 GMT


Sumit Mohanty commented on AMBARI-21099:

Thanks [~oleewere]. So there are three driving factors:
* Ambari-3.x will require jdk8
* Some stacks it supports (say HDP-2.6) will require jdk7
* Some services within the stack may require jdk8 (they happen to be Ambari defaults but in
general we can assume them to be a subset of services)

Today, the same jdk is used for both the Ambari and the services and we also expect that at
some point in future Ambari and the stacks will converge back to using the same jdk. While
this is not a must but in general users will prefer to supply a single jdk.

So, we are looking at users supplying multiple jdks. We can treat it such with one of them
being the default. Existing command.json parameters can map to the default jdk (e.g. 7 for
now). Ambari can demand jdk 8 for itself as part of upgrade or install. We need to figure
out how a service can indicate that it needs jdk 8 (or a jdk version that is not registered
yet). When jdk8 is installed lets just treat it as a second jdk, the same way we allow registration
of multiple jdbc drivers. Let the services, that need jdk8, pick the right variables from
comand json.

We can introduce the notion of a stack/service supplying a min version of jdk required with
default being "don't care and use the user supplied default jdk"

> Drop JDK 7 support for Ambari Server and Ambari managed services (AMS, LogSearch, Infra)
> ----------------------------------------------------------------------------------------
>                 Key: AMBARI-21099
>                 URL:
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 3.0.0
>            Reporter: Olivér Szabó
>            Assignee: Olivér Szabó
>             Fix For: 3.0.0
>         Attachments: AMBARI-21099.patch
> 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 setup
> {code:java}
> Choose 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
> {code}
> 2. If JDK 7 is picked, that cannot be used for ambari (only for the stack services)
> {code:java}
> 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
> {code}
> The following command also can work to setup custom java_home (for stacks + ambari):
> {code:java}
> ambari-server setup -s --java-home=... --stack-java-home=...
> {code}
> After the commands are executed, the following properties would appear in
> {code:java}
> {code}
> 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)

This message was sent by Atlassian JIRA

View raw message