Jialiang Cai created AMBARI-26641:
-------------------------------------
Summary: Separate Ambari and stack JDK configuration after JDK 17
upgrade
Key: AMBARI-26641
URL: https://issues.apache.org/jira/browse/AMBARI-26641
Project: Ambari
Issue Type: Bug
Reporter: Jialiang Cai
h2. Problem
After Ambari Server moved to JDK 17, {{java.home}}, {{ambari.java.home}}, setup
prompts, upgrade migration, Agent Java helpers, and stack service Java settings
can refer to different runtimes without a clear contract. BIGTOP services may
also require JDK versions different from both Ambari Server and the stack
default.
h2. Expected behavior
Use three explicit layers:
* {{ambari.java.home/version}} for Ambari Server, Agent Java helpers, and
Ambari-owned Java checks.
* {{stack.java.home/version}} for the default stack service JDK, with
compatibility fallback from legacy {{java.home}}.
* BIGTOP {{cluster-env/java_home_overrides}} for pre-installed service or
component JDK overrides, with component precedence and safe fallback to the
stack default.
h2. Scope
Fix setup and upgrade migration for JDK 17+, keep Ambari Server and Agent Java
helpers aligned, expose the separated properties through server command
metadata and APIs, validate the actual Java runtime on hosts, update
installation and database helper callers, select JDK-compatible GC options
where needed, and add focused server, agent, and UI tests. Windows behavior is
outside this change.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
