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:11:45 UTC

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

Andrii Tkach created AMBARI-13025:
-------------------------------------

             Summary: 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


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)