Mailing-List: contact ambari-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ambari-dev@incubator.apache.org
Date: Wed, 3 Jul 2013 17:42:22 +0000 (UTC)
From: "Jaimin D Jetly (JIRA)" <jira@apache.org>
To: ambari-dev@incubator.apache.org
Message-ID: <JIRA.12655982.1372838335161.207293.1372873342252@arcas>
In-Reply-To: <JIRA.12655982.1372838335161@arcas>
References: <JIRA.12655982.1372838335161@arcas>
Subject: [jira] [Updated] (AMBARI-2547) Security wizard: Successive
 refreshes at some point results in blank screen.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Jaimin D Jetly updated AMBARI-2547:
-----------------------------------

    Attachment: snapshot_1.png
    
> Security wizard: Successive refreshes at some point results in blank screen.
> ----------------------------------------------------------------------------
>
>                 Key: AMBARI-2547
>                 URL: https://issues.apache.org/jira/browse/AMBARI-2547
>             Project: Ambari
>          Issue Type: Bug
>          Components: client
>    Affects Versions: 1.2.5
>            Reporter: Jaimin D Jetly
>            Assignee: Jaimin D Jetly
>              Labels: security
>             Fix For: 1.2.5
>
>         Attachments: AMBARI-2547.patch, snapshot_1.png
>
>
> h5. This ticket addresses following issues:
> * Refreshing at the moment when none of the stage is running brings up blank screen. The time window for this is small. Once entered in this state, user needs to quit the wizard and go through the wizard again to enable security.
> * On Google chrome multiple refreshes occasionally cancels the request. This calls ajax error callback function which sets the error flag and resets the request Id to its default value. Setting the error flag will mark the stage as failure and show retry button which can be accepted. But setting the request Id to its default value makes retry button fire a API for new request. We should persist the request Id to let the user poll on the same Id on hitting retry button. Ajax call error while polling request shouldn't reset requestId. Only task failures in the polled response data should reset request Id.
> * We keep persisting entire localDb on the server side with the help of an observable function. This is for multiple browser support. This is large amount of data and its noticed to have slower ui on refreshes as refresh  calls the function multiple time. We need to isolate other data and persist only security wizard specific data on the server.   

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira