[jira] [Updated] (AMBARI-12188) Intra stack-version upgrade sends stale configs in commands to hosts

["Srimanth Gunturi (JIRA)" <ji...@apache.org>]

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

Srimanth Gunturi updated AMBARI-12188:
--------------------------------------
    Attachment: AMBARI-12188.patch

Attaching patch. The solution is to basically update the config-tags just before execution of a command. This can be indicated by setting a {{forceRefreshConfigTagsBeforeExecution}} value on the command.

> Intra stack-version upgrade sends stale configs in commands to hosts
> --------------------------------------------------------------------
>
>                 Key: AMBARI-12188
>                 URL: https://issues.apache.org/jira/browse/AMBARI-12188
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.1.0
>            Reporter: Srimanth Gunturi
>            Assignee: Srimanth Gunturi
>             Fix For: 2.1.0
>
>         Attachments: AMBARI-12188.patch
>
>
> When doing an intra stack-version upgrade/downgrade, ambari-server persists config-tags to use at the time of upgrade request. This is problematic when the upgrade process then changes configs, as the persisted commands have the stale tags. 
> This is manifested in the case where Hive service upgrade from HDP-2.3.x stack-version to HDP-2.3.y stack-version results in HiveServer component not starting as both the old and new components use the same configs and conflict on the {{hive.server2.thrift.port}} value. The original port is generally 10000 and the new port should be 10010. However due to stale configs, both the old and new components conflict over the port and the new component does not start.



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