ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Myroslav Papirkovskyi (JIRA)" <>
Subject [jira] [Resolved] (AMBARI-22774) Handle configs update in the middle of request (RU)
Date Mon, 05 Feb 2018 13:00:00 GMT


Myroslav Papirkovskyi resolved AMBARI-22774.
    Resolution: Fixed

Merged into branch-3.0-perf

> Handle configs update in the middle of request (RU)
> ---------------------------------------------------
>                 Key: AMBARI-22774
>                 URL:
>             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
>          Time Spent: 1h 10m
>  Remaining Estimate: 0h
> 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

View raw message