We should add check for contradicting settings in validation phase itself. +1 on that.
Regards, Sandeep On Thu, Jan 21, 2016 at 3:14 AM, Isha Arkatkar (JIRA) <[email protected]> wrote: > > [ > https://issues.apache.org/jira/browse/APEXCORE-10?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15109514#comment-15109514 > ] > > Isha Arkatkar commented on APEXCORE-10: > --------------------------------------- > > In case of anti-affinity and host-locality set among partitions of > operator, yes, we need to set precedence order. > Another option is: should we check for such contradicting settings this in > dag.validate phase itself? > > > 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) >
