[
https://issues.apache.org/jira/browse/AMBARI-20759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15967974#comment-15967974
]
Hadoop QA commented on AMBARI-20759:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12863316/AMBARI-20759.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/11392//console
This message is automatically generated.
> The Web Client Upgrade Wizard Does Not Wait Long Enough When Creating a Large
> Upgrade
> -------------------------------------------------------------------------------------
>
> Key: AMBARI-20759
> URL: https://issues.apache.org/jira/browse/AMBARI-20759
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
> Affects Versions: 2.4.2
> Reporter: Antonenko Alexander
> Assignee: Antonenko Alexander
> Fix For: 2.5.1
>
> Attachments: AMBARI-20759.patch
>
>
> When creating an upgrade on a large cluster, the backend currently takes a
> very long time to create the data and persist it. Although steps are being
> taken to greatly reduce this time, it could still take up to several minutes
> for this request to go through.
> The web client currently doesn't wait long enough for the upgrade to being.
> It will produce an error message saying that the upgrade could not be created
> and then gets confused when the upgrade eventually shows up. It also allows a
> user to try to create another upgrade while the first is still being
> generated.
> STR:
> - Create a rolling upgrade on a cluster with 1000 hosts where every host has
> 15 components installed.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
