[jira] [Commented] (AMBARI-5778) In some upgrade scenarios, Ambari Web's persist key-value store state causes the UI to act unpredictably

["Siddharth Wagle (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/AMBARI-5778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13999079#comment-13999079 ] 

Siddharth Wagle commented on AMBARI-5778:
-----------------------------------------

+1 for the patch

> In some upgrade scenarios, Ambari Web's persist key-value store state causes the UI to act unpredictably
> --------------------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-5778
>                 URL: https://issues.apache.org/jira/browse/AMBARI-5778
>             Project: Ambari
>          Issue Type: Bug
>          Components: controller
>    Affects Versions: 1.5.1
>            Reporter: Myroslav Papirkovskyy
>            Assignee: Myroslav Papirkovskyy
>            Priority: Critical
>             Fix For: 1.6.0
>
>         Attachments: AMBARI-5778.patch
>
>
> During Ambari upgrade, automatically clear the persist state to prevent potential issues with Ambari Web not working properly (this was observed a number of times on upgraded clusters). 
> Currently, we make the following call to get out of the inconsistent state so that Ambari Web works properly:
> {code}
> curl -i -u admin:admin -H "X-Requested-By: ambari" -X POST -d '{ "CLUSTER_CURRENT_STATUS": "{\"clusterState\":\"CLUSTER_STARTED_5\"}" }' http://localhost:8080/api/v1/persist
> {code}
> We need to do something equivalent during upgrade.



--
This message was sent by Atlassian JIRA
(v6.2#6252)