[
https://issues.apache.org/jira/browse/AMBARI-13025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14733987#comment-14733987
]
Hudson commented on AMBARI-13025:
---------------------------------
SUCCESS: Integrated in Ambari-trunk-Commit #3396 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/3396/])
AMBARI-13025 Switching config versions results in 'Restart Required' message
showing up with delay. (atkach) (atkach:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=45c172f3b5ff0a77a4f7d8739a09be4640c5b367)
* ambari-web/test/views/common/configs/config_history_flow_test.js
* ambari-web/app/controllers/global/cluster_controller.js
* ambari-web/app/views/common/configs/config_history_flow.js
> 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: AMBARI-13025.patch, 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)
