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

Hudson commented on AMBARI-24116:
---------------------------------

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #9478 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/9478/])
AMBARI-24116 Web Client Pulls Back Too Much Information in Upgrade 
(1963907+atkach: 
[https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=d9b7a28430cddc2f0388301a18843fb8f89f622b])
* (edit) ambari-web/app/views/main/admin/stack_upgrade/upgrade_task_view.js
* (edit) ambari-web/app/views/main/admin/stack_upgrade/upgrade_group_view.js
* (edit) 
ambari-web/test/views/main/admin/stack_upgrade/upgrade_task_view_test.js
* (edit) 
ambari-web/app/templates/main/admin/stack_upgrade/stack_upgrade_wizard.hbs
* (edit) ambari-web/app/templates/main/admin/stack_upgrade/upgrade_task.hbs


> Web Client Pulls Back Too Much Information in Upgrade Wizard
> ------------------------------------------------------------
>
>                 Key: AMBARI-24116
>                 URL: https://issues.apache.org/jira/browse/AMBARI-24116
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-web
>    Affects Versions: 2.7.0
>            Reporter: Andrii Tkach
>            Assignee: Andrii Tkach
>            Priority: Critical
>              Labels: pull-request-available
>             Fix For: 2.7.0
>
>         Attachments: upgrade.png
>
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> During an upgrade, the upgrade wizard is very inefficient at the data that it 
> pulls back. On larger upgrades, expanding groups in progress is practically 
> unusable and can actually cause the browser to crash.
> I recently observed this on a small upgrade but quickly opening and closing 
> the active group (see screenshot). The expansion of groups/tasks just sat 
> there spinning.
> I think that the upgrade wizard needs to pull back a lot less data and 
> possibly cache the majority of what it has in order to make it usable during 
> a larger upgrade.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to