You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@apex.apache.org by "Sasha Parfenov (JIRA)" <ji...@apache.org> on 2015/12/30 00:50:49 UTC

[jira] [Updated] (APEXCORE-10) Enable non-affinity of operators per node (not containers)

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

Sasha Parfenov updated APEXCORE-10:
-----------------------------------
    Labels: roadmap  (was: )

> 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)