ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinod Kumar Vavilapalli (JIRA)" <>
Subject [jira] [Updated] (AMBARI-194) Avoid TxnProgressWidget Getting Stuck In An Infinite Loop
Date Wed, 04 Jul 2012 21:50:37 GMT


Vinod Kumar Vavilapalli updated AMBARI-194:

    Fix Version/s:     (was: ambari-186)
> Avoid TxnProgressWidget Getting Stuck In An Infinite Loop
> ---------------------------------------------------------
>                 Key: AMBARI-194
>                 URL:
>             Project: Ambari
>          Issue Type: Bug
>    Affects Versions: ambari-186
>            Reporter: Varun Kapoor
>            Assignee: Varun Kapoor
>            Priority: Critical
>             Fix For: 0.9.0
>         Attachments: AMBARI-194.patch
>   Original Estimate: 4h
>  Remaining Estimate: 4h
> php/frontend/fetchTxnProgress.php's response JSON checks that at least one subTxn is
in progress, or it sets the top-level 'progress' key to null. The JS checks for this null-ness
before deciding to swap the loading image for the list of progress states. 
> Sadly, when the backend txn is a no-op (for instance, when a service is already started
but a user starts it again from the Manage Services page), none of the subTxns will be in-progress,
causing this condition to be triggered. Thus, no-ops lead to the loading image showing forever,
with no way for users to break the cycle, which is pretty darn bad.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message