apex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (APEXCORE-10) Enable non-affinity of operators per node (not containers)
Date Sat, 26 Mar 2016 01:33:25 GMT

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

ASF GitHub Bot commented on APEXCORE-10:
----------------------------------------

Github user ishark commented on a diff in the pull request:

    https://github.com/apache/incubator-apex-core/pull/250#discussion_r57506744
  
    --- Diff: api/pom.xml ---
    @@ -70,14 +70,6 @@
               <groupId>commons-beanutils</groupId>
             </exclusion>
             <exclusion>
    -          <artifactId>jackson-core-asl</artifactId>
    --- End diff --
    
    This was added for supporting setting of Affinity Rules from properties.xml. Added a JsonStringCodec
for reading Affinity Rule Json..


> Enable non-affinity of operators per node (not containers)
> ----------------------------------------------------------
>
>                 Key: APEXCORE-10
>                 URL: https://issues.apache.org/jira/browse/APEXCORE-10
>             Project: Apache Apex Core
>          Issue Type: Task
>            Reporter: Amol Kekre
>            Assignee: Isha Arkatkar
>              Labels: roadmap
>
> The issue happens on cloud which provides virtual cores with software like Xen underneath.
In effect if CPU intensive operators land up on same node we have a resource bottleneck,
> Need to create an attribute that does the following
> - Operators A & B should not be on same node
> - Stram should use this attribute to try to get containers on different node
> It is understood that the user is making an explicit choice to use NIC instead of stream
local optimization



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

Mime
View raw message