apex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (APEXCORE-10) Enable non-affinity of operators per node (not containers)
Date Sat, 26 Mar 2016 01:19:25 GMT

    [ https://issues.apache.org/jira/browse/APEXCORE-10?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15212694#comment-15212694
] 

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_r57506464
  
    --- Diff: api/src/main/java/com/datatorrent/api/AffinityRule.java ---
    @@ -0,0 +1,211 @@
    +/**
    + * Licensed to the Apache Software Foundation (ASF) under one
    + * or more contributor license agreements.  See the NOTICE file
    + * distributed with this work for additional information
    + * regarding copyright ownership.  The ASF licenses this file
    + * to you under the Apache License, Version 2.0 (the
    + * "License"); you may not use this file except in compliance
    + * with the License.  You may obtain a copy of the License at
    + *
    + *   http://www.apache.org/licenses/LICENSE-2.0
    + *
    + * Unless required by applicable law or agreed to in writing,
    + * software distributed under the License is distributed on an
    + * "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
    + * KIND, either express or implied.  See the License for the
    + * specific language governing permissions and limitations
    + * under the License.
    + */
    +package com.datatorrent.api;
    +
    +import java.io.Serializable;
    +import java.util.List;
    +
    +import com.datatorrent.api.DAG.Locality;
    +
    +/**
    + * Affinity rule specifies constraints for physical deployment of operator
    + * containers. There are two types of rules that can be specified: Affinity and
    + * Anti-affinity. Each rule contains list of operators or pair of 2 operators or
    + * a regex that should match at least 2 operators. Based on the type of rule,
    + * affinity or anti-affinity, the operators will be deployed together or away
    + * from each other. The locality indicates the level at which the rule should be
    + * applied. E.g. CONTAINER_LOCAL affinity would indicate operators Should be
    + * allocated within same container NODE_LOCAL anti-affinity indicates that the
    + * operators should not be allocated on the same node. The rule can be either
    + * strict or relaxed.
    + *
    + */
    +public class AffinityRule implements Serializable
    +{
    +  @Override
    +  public String toString()
    +  {
    +    return "AffinityRule {operatorsList=" + operatorsList + ", operatorRegex=" + operatorRegex
+ ", operators="
    +        + operators + ", locality=" + locality + ", type=" + type + ", relaxLocality="
+ relaxLocality + "}";
    +  }
    +
    +  private static final long serialVersionUID = 107131504929875386L;
    +
    +  /**
    +   * Pair of operator names to specify affinity rule
    +   * The order of operators is not considered in this class
    +   * i.e. OperatorPair("O1", "O2") is equal to OperatorPair("O2", "O1")
    +   */
    +  public static class OperatorPair implements Serializable
    --- End diff --
    
    Why is it a pair and not a collection, looks like the regex can match more operators?


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

Mime
View raw message