You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Olivér Szabó (JIRA)" <ji...@apache.org> on 2017/05/25 11:46:04 UTC

[jira] [Updated] (AMBARI-21099) Drop JDK 7 support for Ambari Server and Ambari managed services (AMS, LogSearch,Infra)

     [ https://issues.apache.org/jira/browse/AMBARI-21099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Olivér Szabó updated AMBARI-21099:
----------------------------------
    Summary: Drop JDK 7 support for Ambari Server and Ambari managed services (AMS, LogSearch,Infra)  (was: Drop JDK 7 support for Ambari Server and Ambari managed services)

> Drop JDK 7 support for Ambari Server and Ambari managed services (AMS, LogSearch,Infra)
> ---------------------------------------------------------------------------------------
>
>                 Key: AMBARI-21099
>                 URL: https://issues.apache.org/jira/browse/AMBARI-21099
>             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}
> After the commands are executed, the following properties would appear in ambari.properties
> {code:java}
> stack.java.home=/usr/jdk64/jdk1.7.0_67
> stack.jdk.name=jdk-7u67linux-x64.tar.gz
> stack.jce.name=UnlimitedJCEPolicyJDK7.zip
> {code}
> or opposite of it:
> {code:java}
> ambari.java.home=/usr/jdk64/jdk1.8.0_112
> ambari.jdk.name=jdk-8u112linux-x64.tar.gz
> ambari.jce.name=UnlimitedJCEPolicyJDK8.zip
> {code}
> During command.json generating, hostParameters would be filled with the proper jdk,jce info (different for infra/logsearch/ams from other services)
> Also that requires to add JDK version check at the start of the ambari-upgrade. (tell the user to call ambari-server setup first)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)