From yarn-issues-return-138757-archive-asf-public=cust-asf.ponee.io@hadoop.apache.org Wed Feb 28 01:45:06 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id 97568180651 for ; Wed, 28 Feb 2018 01:45:05 +0100 (CET) Received: (qmail 96868 invoked by uid 500); 28 Feb 2018 00:45:03 -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 96857 invoked by uid 99); 28 Feb 2018 00:45:03 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 28 Feb 2018 00:45:03 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 44B34C0046 for ; Wed, 28 Feb 2018 00:45:03 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -110.311 X-Spam-Level: X-Spam-Status: No, score=-110.311 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, RCVD_IN_DNSWL_MED=-2.3, 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 (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id SkNlUH5MzblH for ; Wed, 28 Feb 2018 00:45:02 +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 702215F5AF for ; Wed, 28 Feb 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 76D77E01AB for ; Wed, 28 Feb 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 2ABE1240BA for ; Wed, 28 Feb 2018 00:45:00 +0000 (UTC) Date: Wed, 28 Feb 2018 00:45:00 +0000 (UTC) From: "Arun Suresh (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YARN-7929) SLS supports setting container execution 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-7929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16379579#comment-16379579 ] Arun Suresh commented on YARN-7929: ----------------------------------- bq. it looks to me like the O containers are still launched based on the allocated resource instead of the actual utilization right? yup I just saw the bit regarding {{yarn.nodemanager.resource.utilization.ratio}}. I agree, we need to think a bit more before we incorporate this. Just to clarify, with this patch, irrespective of what this ratio is, if an AM requests an OPP containers, it will get the token and a container will be launched right ? I can buy the argument that the SLS is technically supposed to simulate the "scheduler" so we can defer actually fixing the NMSimulator to later. So, think we can go ahead with the commit - but to truly simulate a cluster, we need YARN-6826 > SLS supports setting container execution > ---------------------------------------- > > Key: YARN-7929 > URL: https://issues.apache.org/jira/browse/YARN-7929 > Project: Hadoop YARN > Issue Type: Sub-task > Components: scheduler-load-simulator > Reporter: Jiandan Yang > Assignee: Jiandan Yang > Priority: Major > Attachments: YARN-7929.001.patch, YARN-7929.002.patch, YARN-7929.003.patch, YARN-7929.004.patch, YARN-7929.005.patch, YARN-7929.006.patch > > > SLS currently support three tracetype, SYNTH, SLS and RUMEN, but trace file can not set execution type of container. > This jira will introduce execution type in SLS to help better simulation. This will help the perf testing with regarding to the Opportunistic Containers. > RUMEN has default execution type GUARANTEED > SYNTH set execution type by field map_execution_type and reduce_execution_type > SLS set execution type by field container.execution_type > For compatibility set GUARANTEED as default value when not setting above fields in trace file -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org For additional commands, e-mail: yarn-issues-help@hadoop.apache.org