Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id DF876200CE5 for ; Sat, 8 Jul 2017 02:01:50 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id DC69F16A53F; Sat, 8 Jul 2017 00:01:50 +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 2E46C16A53E for ; Sat, 8 Jul 2017 02:01:50 +0200 (CEST) Received: (qmail 75891 invoked by uid 500); 8 Jul 2017 00:01:49 -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 75880 invoked by uid 99); 8 Jul 2017 00:01:49 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 08 Jul 2017 00:01:49 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id E5070C18E2 for ; Sat, 8 Jul 2017 00:01:48 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.002 X-Spam-Level: X-Spam-Status: No, score=-100.002 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id 5Eqsxw7Y60Pu for ; Sat, 8 Jul 2017 00:01:48 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id E259B5FC9D for ; Sat, 8 Jul 2017 00:01:44 +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 B160FE0E38 for ; Sat, 8 Jul 2017 00:01:42 +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 4E4C4246E8 for ; Sat, 8 Jul 2017 00:01:37 +0000 (UTC) Date: Sat, 8 Jul 2017 00:01:37 +0000 (UTC) From: "Haibo Chen (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YARN-6685) Add job count in to SLS JSON input format MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Sat, 08 Jul 2017 00:01:51 -0000 [ https://issues.apache.org/jira/browse/YARN-6685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16078855#comment-16078855 ] Haibo Chen commented on YARN-6685: ---------------------------------- Thanks [~yufeigu] for the patch! The patch looks good to me in general. One thing that's good to have is to document the behavior of job.count in SLS documentation especially because now that job.id takes no effect if job.count > 1. > Add job count in to SLS JSON input format > ----------------------------------------- > > Key: YARN-6685 > URL: https://issues.apache.org/jira/browse/YARN-6685 > Project: Hadoop YARN > Issue Type: Sub-task > Components: scheduler-load-simulator > Affects Versions: 3.0.0-alpha3 > Reporter: Yufei Gu > Assignee: Yufei Gu > Attachments: YARN-6685.001.patch > > > YARN-6522 made writing SLS workload much simpler by improving SLS JSON input format. There is one more improvement we can do. We can add job count to simplify configuration of multiple job with the same configuration. -- 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