ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-19035) LLAP startup: Ambari should not use slider anti-affinity when it's avoidable
Date Thu, 01 Dec 2016 04:04:58 GMT

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

Hadoop QA commented on AMBARI-19035:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12841175/AMBARI-19035.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/9472//console

This message is automatically generated.

> LLAP startup: Ambari should not use slider anti-affinity when it's avoidable
> ----------------------------------------------------------------------------
>
>                 Key: AMBARI-19035
>                 URL: https://issues.apache.org/jira/browse/AMBARI-19035
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.4.1
>            Reporter: Swapan Shridhar
>            Assignee: Swapan Shridhar
>            Priority: Critical
>             Fix For: 2.5.0
>
>         Attachments: AMBARI-19035.patch
>
>
> - YARN does not support anti-affinity, and therefore Slider implements AA by the means
of exclusion lists - it starts containers one by one and excludes the nodes it gets; that
adds ~2sec./machine of overhead (on openstack).
> - When the LLAP container memory size configuration is more than half of YARN node memory,
or the same for number of cores, AA is implicit and should be avoided.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message