From yarn-issues-return-134497-archive-asf-public=cust-asf.ponee.io@hadoop.apache.org Wed Jan 10 01:45:05 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 C8ACE180718 for ; Wed, 10 Jan 2018 01:45:05 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id B83AE160C3F; Wed, 10 Jan 2018 00:45:05 +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 0AE47160C17 for ; Wed, 10 Jan 2018 01:45:04 +0100 (CET) Received: (qmail 37569 invoked by uid 500); 10 Jan 2018 00:45:04 -0000 Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list yarn-issues@hadoop.apache.org Received: (qmail 37558 invoked by uid 99); 10 Jan 2018 00:45:04 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 10 Jan 2018 00:45:04 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id AEBA51807A9 for ; Wed, 10 Jan 2018 00:45:03 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -107.911 X-Spam-Level: X-Spam-Status: No, score=-107.911 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, KAM_ASCII_DIVIDERS=0.8, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id s1kv429nA9BQ for ; Wed, 10 Jan 2018 00:45:03 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id C7B475FB71 for ; Wed, 10 Jan 2018 00:45:01 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id C6A58E256E for ; Wed, 10 Jan 2018 00:45:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 284A8240FE for ; Wed, 10 Jan 2018 00:45:00 +0000 (UTC) Date: Wed, 10 Jan 2018 00:45:00 +0000 (UTC) From: "Weiwei Yang (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YARN-7681) Scheduler should double-check placement constraint before actual allocation is made MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/YARN-7681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16319470#comment-16319470 ] Weiwei Yang commented on YARN-7681: ----------------------------------- Thanks [~asuresh] and [~pgaref], uploaded v2 patch to fix the chechstyle issue. > Scheduler should double-check placement constraint before actual allocation is made > ----------------------------------------------------------------------------------- > > Key: YARN-7681 > URL: https://issues.apache.org/jira/browse/YARN-7681 > Project: Hadoop YARN > Issue Type: Sub-task > Components: RM, scheduler > Reporter: Weiwei Yang > Assignee: Weiwei Yang > Attachments: YARN-7681-YARN-6592.001.patch, YARN-7681-YARN-6592.002.patch > > > This JIRA is created based on the discussions under YARN-7612, see comments after [this comment|https://issues.apache.org/jira/browse/YARN-7612?focusedCommentId=16303051&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16303051]. AllocationTagsManager maintains tags info that helps to make placement decisions at placement phase, however tags are changing along with container's lifecycle, so it is possible that the placement violates the constraints at the scheduling phase. Propose to add an extra check in the scheduler to make sure constraints are still satisfied during the actual allocation. -- This message was sent by Atlassian JIRA (v6.4.14#64029) --------------------------------------------------------------------- To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org For additional commands, e-mail: yarn-issues-help@hadoop.apache.org