Mailing-List: contact dev-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Tue, 17 Dec 2013 19:40:06 +0000 (UTC)
From: "Antonenko Alexander (JIRA)" <jira@apache.org>
To: dev@ambari.apache.org
Message-ID: <JIRA.12685178.1387290450871.52120.1387309206921@arcas>
In-Reply-To: <JIRA.12685178.1387290450871@arcas>
References: <JIRA.12685178.1387290450871@arcas>
Subject: [jira] [Updated] (AMBARI-4088) UI doesn't select all hosts on
 Assign Slaves step sometimes
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Antonenko Alexander updated AMBARI-4088:
----------------------------------------

    Attachment: AMBARI-4088_additional_patch_1.4.3.patch

> UI doesn't select all hosts on Assign Slaves step sometimes
> -----------------------------------------------------------
>
>                 Key: AMBARI-4088
>                 URL: https://issues.apache.org/jira/browse/AMBARI-4088
>             Project: Ambari
>          Issue Type: Bug
>          Components: client
>    Affects Versions: 1.4.2
>            Reporter: Antonenko Alexander
>            Assignee: Antonenko Alexander
>            Priority: Critical
>             Fix For: 1.4.3
>
>         Attachments: AMBARI-4088.patch, AMBARI-4088_additional_patch.patch, AMBARI-4088_additional_patch_1.4.3.patch
>
>
> When deploying large cluster (>600 nodes) UI not always selects all hosts on assign slaves step.
> For example on last reproduce, it selected only 336 of 600 expected slaves.
> Actually theres workaround, on review step you can see that there's less slaves then expected and return to assign slaves step, but then you have to repeat all following steps.
> It looks like select event is triggered earlier then all host rows loaded as unselected hosts are always last ones.


--
This message was sent by Atlassian JIRA
(v6.1.4#6159)