[
https://issues.apache.org/jira/browse/APEXCORE-10?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15212777#comment-15212777
]
ASF GitHub Bot commented on APEXCORE-10:
----------------------------------------
Github user tweise commented on a diff in the pull request:
https://github.com/apache/incubator-apex-core/pull/250#discussion_r57508918
--- Diff:
engine/src/main/java/com/datatorrent/stram/StreamingAppMasterService.java ---
@@ -668,7 +671,10 @@ private void execute() throws YarnException,
IOException
int numReleasedContainers = 0;
int nextRequestPriority = 0;
ResourceRequestHandler resourceRequestor = new
ResourceRequestHandler();
+ // Use override for container requestor in case of cloudera
distribution,to handle host specific requests
+ ContainerRequestHandler containerRequestor =
System.getenv().containsKey("CDH_HADOOP_BIN") ? new
ContainerRequestHandlerCloudera() : new ContainerRequestHandler();
--- End diff --
Would it makes sense to combine ResourceRequestHandler and
ContainerRequestHandler?
> 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)
