[jira] [Assigned] (AMBARI-17280) RU to write out client configs that are dependencies of Hive, ATS, and Oozie during upgrades that change configs

["Alejandro Fernandez (JIRA)" <ji...@apache.org>]

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

Alejandro Fernandez reassigned AMBARI-17280:
--------------------------------------------

    Assignee: Alejandro Fernandez

> RU to write out client configs that are dependencies of Hive, ATS, and Oozie during upgrades that change configs
> ----------------------------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-17280
>                 URL: https://issues.apache.org/jira/browse/AMBARI-17280
>             Project: Ambari
>          Issue Type: Bug
>          Components: stacks
>    Affects Versions: 2.2.0
>            Reporter: Alejandro Fernandez
>            Assignee: Alejandro Fernandez
>            Priority: Critical
>             Fix For: 2.4.0
>
>
> During RU, HiveServer2 is restarted but the newer tez configs have not yet been saved, which is incorrect because Hive has a dependency on Tez.
> This is important when configs change during a major stack upgrade, e.g., HDP 2.4 -> 2.5. What happens today is,
> * Install packages generates /etc/tez/2.5.0.0-1/0 and copies the configs from /etc/tez/2.4.0.0-1/0/ to the new folder
> * If configs change during RU, then Hive is restarted and the classpath means that it will pick up the older tez configs from the new /etc/tez/2.5.0.0-1/0 folder
> This problem exists for all of these components:
> HiveServer: depends on Tez and MapReduce clients
> ATS: depends on Tez and Spark clients
> Oozie: depends on Tez, Spark, and MapReduce clients
> This problem only exists when configs change (so crossing major stack version) and during RU (because it is allowed to change configs during the middle of restarting services).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)