Uploaded image for project: 'Ambari'
  1. Ambari
  2. AMBARI-5778

In some upgrade scenarios, Ambari Web's persist key-value store state causes the UI to act unpredictably

Log workAgile BoardRank to TopRank to BottomAttach filesAttach ScreenshotBulk Copy AttachmentsBulk Move AttachmentsVotersWatch issueWatchersCreate sub-taskConvert to sub-taskLinkCloneLabelsUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Critical
    • Resolution: Fixed
    • 1.5.1
    • 1.6.0
    • ambari-server
    • None

    Description

      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:

      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

      We need to do something equivalent during upgrade.

      Attachments

        Activity
          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            mpapirkovskyy Papirkovskyy Myroslav Assign to me
            mpapirkovskyy Papirkovskyy Myroslav
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment