[
https://issues.apache.org/jira/browse/APEXCORE-10?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15176963#comment-15176963
]
ASF GitHub Bot commented on APEXCORE-10:
----------------------------------------
Github user ishark commented on the pull request:
https://github.com/apache/incubator-apex-core/pull/250#issuecomment-191536790
Testing Done:
1. Unit tests for Dag Validation scenarios
2. Unit tests for host allocation based on affinity rules
3. Tested following scenarios on Cloudera and Hortonworks:
- Anti-affinity between partitions of operators
- Anti-affinity between any two operators (stream connected and not
connected)
- Anti-affinity between parallel partitioned operators
- Node and Container Affinity between operators not connected by stream
- Node affinity between 2 Stream connected operators when the stream is
not Node Local
- Container affinity between 2 Stream connected operators when the
stream is not Node Local
- Affinity and Anti-affinity rules with Locality_host set for operator
- Out of resources condition in case of Strict Anti-affinity.
Application should keep waiting till resources are allocated as per rules
- Checked preferred anti-affinity rules are dropped if resources are not
available
> 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)
