[
https://issues.apache.org/jira/browse/AMBARI-4088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13850494#comment-13850494
]
Antonenko Alexander commented on AMBARI-4088:
---------------------------------------------
This happens due to lazy loading hosts, when we click "select all" not all
hosts are loaded to UI, so we will select only hosts that are already loaded at
that moment.
> 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
>
>
> 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)
