[
https://issues.apache.org/jira/browse/APEXCORE-10?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15138028#comment-15138028
]
Isha Arkatkar commented on APEXCORE-10:
---------------------------------------
Here is archive link to discussion on dev@apex:
http://mail-archives.apache.org/mod_mbox/apex-dev/201602.mbox/%3CCAL9V3e%3Da7JRqTiK46a%2B6%2BhkZGH%2BWK8-bZgSr6P-d_Y%2B9VB7rrA%40mail.gmail.com%3E
> 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)
