You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Andrii Tkach (JIRA)" <ji...@apache.org> on 2015/09/07 16:12:45 UTC

[jira] [Updated] (AMBARI-13025) Switching config versions results in 'Restart Required' message showing up with delay

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

Andrii Tkach updated AMBARI-13025:
----------------------------------
    Attachment: timeline.png
                Screen Shot 2015-08-12 at 1.30.44 PM.png
                network-log-screenshot.png

> Switching config versions results in 'Restart Required' message showing up with delay
> -------------------------------------------------------------------------------------
>
>                 Key: AMBARI-13025
>                 URL: https://issues.apache.org/jira/browse/AMBARI-13025
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-web
>    Affects Versions: 2.1.0
>            Reporter: Andrii Tkach
>            Assignee: Andrii Tkach
>            Priority: Critical
>             Fix For: 2.1.2
>
>         Attachments: Screen Shot 2015-08-12 at 1.30.44 PM.png, network-log-screenshot.png, timeline.png
>
>
> In ZK service I had 5 different config versions and the service was all in-sync. Then I made an older version current. After like 5s the 'Restart Required' message showed up. This problem becomes worse on larger clusters - it took 20s on a 20 node cluster etc.
> We need to see if UI is updating the status with such delay, or if there is a specific API that is slow to provide the updated status. If it is an API issue, please specify the exact API and turn it into a BE issue.



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