[jira] [Updated] (AMBARI-22774) Handle configs update in the middle of request (RU)

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

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

ASF GitHub Bot updated AMBARI-22774:
------------------------------------
    Labels: pull-request-available  (was: )

> Handle configs update in the middle of request (RU)
> ---------------------------------------------------
>
>                 Key: AMBARI-22774
>                 URL: https://issues.apache.org/jira/browse/AMBARI-22774
>             Project: Ambari
>          Issue Type: Task
>          Components: ambari-server
>    Affects Versions: 3.0.0
>            Reporter: Myroslav Papirkovskyi
>            Assignee: Myroslav Papirkovskyi
>            Priority: Critical
>              Labels: pull-request-available
>             Fix For: 3.0.0
>
>
> Async events should support RU scenario.
> Main concern: RU process involves server execution commands which may change configs in the middle of request processing, so all new tasks should be executed with new configs.
> Currently this is achieved by mutating config with tag used on request construction.
> We may achieve similar result by implementing upgrade mode (with flag or by analyzing upgrades in progress similar to UI) and when it is enabled intercept execution commands events and extend them with actual configs just before sending to message broker.
> In this case we can also consider to force agent refresh configs when RU finishes.
> Current upgrade process relies on disabling auto-start of components prior to upgrade and doesn't care about status commands (as their configs usually don't change dramatically)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)