From hdfs-dev-return-31395-archive-asf-public=cust-asf.ponee.io@hadoop.apache.org Fri Jan 26 18:28:06 2018 Return-Path: X-Original-To: archive-asf-public@eu.ponee.io Delivered-To: archive-asf-public@eu.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by mx-eu-01.ponee.io (Postfix) with ESMTP id 95393180657 for ; Fri, 26 Jan 2018 18:28:06 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 855F7160C3E; Fri, 26 Jan 2018 17:28:06 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id CB5C1160C20 for ; Fri, 26 Jan 2018 18:28:05 +0100 (CET) Received: (qmail 73900 invoked by uid 500); 26 Jan 2018 17:28:04 -0000 Mailing-List: contact hdfs-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list hdfs-dev@hadoop.apache.org Received: (qmail 73868 invoked by uid 99); 26 Jan 2018 17:28:04 -0000 Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 26 Jan 2018 17:28:04 +0000 Received: from mail-it0-f46.google.com (mail-it0-f46.google.com [209.85.214.46]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id C1A011A0044; Fri, 26 Jan 2018 17:28:03 +0000 (UTC) Received: by mail-it0-f46.google.com with SMTP id p139so1359571itb.1; Fri, 26 Jan 2018 09:28:03 -0800 (PST) X-Gm-Message-State: AKwxytdwk5/bzdva/7rUkvgJibSt6vVBQXCWYlOcT4pqtz62KbEJ+PaX B8PrHPC2720ioGPBCwVhNG2tvASPBG9ayT52vj0= X-Google-Smtp-Source: AH8x224Z7TIl7L2G8KHxMpUyXnSsX+GH6jZe+Wp9IqsZaCD0AfK8yrsACskR0ymTF1d3Uk7fwO6ZdyreUYt1KaQX9NY= X-Received: by 10.36.94.144 with SMTP id h138mr3379523itb.34.1516987680991; Fri, 26 Jan 2018 09:28:00 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Sunil G Date: Fri, 26 Jan 2018 17:27:50 +0000 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [VOTE] Merge YARN-6592 feature branch to trunk To: Arun Suresh Cc: yarn-dev@hadoop.apache.org, Konstantinos Karanasos , Wangda Tan , Weiwei Yang , Panagiotis Garefalakis , Chris Douglas , Carlo Aldo Curino , Subramaniam Krishnan , Vinod Kumar Vavilapalli , Hdfs-dev , Hadoop Common Content-Type: multipart/alternative; boundary="001a11424d70dab0b60563b13735" --001a11424d70dab0b60563b13735 Content-Type: text/plain; charset="UTF-8" +1 - Sunil On Fri, Jan 26, 2018 at 8:58 PM Arun Suresh wrote: > Hello yarn-dev@ > > Based on the positive feedback from the DISCUSS thread [1], I'd like to > start a formal vote to merge YARN-6592 [2] to trunk. The vote will run for > 5 days, and will end Jan 31 7:30AM PDT. > > This feature adds support for placing containers in YARN using rich > placement constraints. For example, this can be used by applications to > co-locate containers on a node or rack (*affinity *constraint), spread > containers across nodes or racks (*anti-affinity* constraint), or even > specify the maximum number of containers on a node/rack (*cardinality * > constraint). > > We have integrated this feature into the Distributed-Shell application for > feature testing. We have performed end-to-end testing on moderately-sized > clusters to verify that constraints work fine. Performance tests have been > done via both SLS tests and Capacity Scheduler performance unit tests, and > no regression was found. We have opened a JIRA to track Jenkins acceptance > of the aggregated patch [3]. Documentation is in the process of being > completed [4]. You can also check our design document for more details [5]. > > Config flags are needed to enable this feature and it should not have any > effect on YARN when turned off. Once merged, we plan to work on further > improvements, which can be tracked in the umbrella YARN-7812 [6]. > > Kindly do take a look at the branch and raise issues/concerns that need to > be addressed before the merge. > > Many thanks to Konstantinos, Wangda, Panagiotis, Weiwei, and Sunil for > their contributions to this effort, as well as Subru, Chris, Carlo, and > Vinod for their inputs and discussions. > > > Cheers > -Arun > > [1] > http://mail-archives.apache.org/mod_mbox/hadoop-yarn-dev/201801.mbox/%3CCAMreUaz%3DGnsjOLZ%3Dem2x%3DQS7qh27euCWNw6Bo_4Cu%2BfXnXhyNA%40mail.gmail.com%3E > [2] https://issues.apache.org/jira/browse/YARN-6592 > [3] https://issues.apache.org/jira/browse/YARN-7792 > [4] https://issues.apache.org/jira/browse/YARN-7780 > [5] > https://issues.apache.org/jira/secure/attachment/12867869/YARN-6592-Rich-Placement-Constraints-Design-V1.pdf > [6] https://issues.apache.org/jira/browse/YARN-7812 > --001a11424d70dab0b60563b13735--