You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Andrii Tkach (JIRA)" <ji...@apache.org> on 2018/06/18 07:41:00 UTC

[jira] [Commented] (AMBARI-24116) Web Client Pulls Back Too Much Information in Upgrade Wizard

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

Andrii Tkach commented on AMBARI-24116:
---------------------------------------

committed to trunk

> 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)