From yarn-issues-return-136887-archive-asf-public=cust-asf.ponee.io@hadoop.apache.org Thu Feb 1 03:18:04 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 1DBD018066D for ; Thu, 1 Feb 2018 03:18:04 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 0E31E160C56; Thu, 1 Feb 2018 02:18:04 +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 53B24160C55 for ; Thu, 1 Feb 2018 03:18:03 +0100 (CET) Received: (qmail 83489 invoked by uid 500); 1 Feb 2018 02:18:02 -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 83477 invoked by uid 99); 1 Feb 2018 02:18:02 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Feb 2018 02:18:02 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id E82411A03E2 for ; Thu, 1 Feb 2018 02:18:01 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -101.511 X-Spam-Level: X-Spam-Status: No, score=-101.511 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id sN61QwK-ntsj for ; Thu, 1 Feb 2018 02:18:01 +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 DAB6D5F296 for ; Thu, 1 Feb 2018 02:18:00 +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 6E75BE01A7 for ; Thu, 1 Feb 2018 02:18: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 2065921E84 for ; Thu, 1 Feb 2018 02:18:00 +0000 (UTC) Date: Thu, 1 Feb 2018 02:18:00 +0000 (UTC) From: "wangwj (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Comment Edited] (YARN-7859) New feature: add queue scheduling deadLine in fairScheduler. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/YARN-7859?page=3Dcom.atlassian.= jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D16346= 762#comment-16346762 ]=20 wangwj edited comment on YARN-7859 at 2/1/18 2:17 AM: ------------------------------------------------------ In my cluster,I did an experiment. There are two queues in my cluster: !screenshot-1.png!=20 And the configuration associated with this issue are :=20 !screenshot-3.png!=20 And I run two jobs in each queue. Of course,before the experiment, I add some log In the code. After two jobs completed,I intercepted some of the logs... From the log we can see one queue has scheduled mandatory if the queue was = not scheduled within 3S. was (Author: wangwj): In my cluster,I did an experiment. There are two queues in my cluster: !screenshot-1.png!=20 And the configuration associated with this issue are :=20 !image-2018-02-01-10-16-55-271.png!=20 And I run two jobs in each queue. Of course,before the experiment, I add some log In the code. After two jobs completed,I intercepted some of the logs... From the log we can see one queue has scheduled mandatory if the queue was = not scheduled within 3S. > New feature: add queue scheduling deadLine in fairScheduler. > ------------------------------------------------------------ > > Key: YARN-7859 > URL: https://issues.apache.org/jira/browse/YARN-7859 > Project: Hadoop YARN > Issue Type: New Feature > Components: fairscheduler > Affects Versions: 3.0.0 > Reporter: wangwj > Priority: Major > Labels: fairscheduler, features, patch > Fix For: 3.0.0 > > Attachments: YARN-7859-v1.patch, log, screenshot-1.png, screensho= t-3.png > > Original Estimate: 24h > Remaining Estimate: 24h > > =C2=A0As everyone knows.In FairScheduler the phenomenon of queue sche= duling starvation often occurs when the number of cluster jobs is large.The= App in one or more queue are pending.So I have thought a way to solve this= problem.Add queue scheduling deadLine in fairScheduler.When a queue is not= scheduled for FairScheduler within a specified time.We mandatory scheduler= it! > Now the way of community solves queue scheduling to starvation is pre= empt container.But this way may increases the failure rate of the job. > On the basis of the above, I propose this issue... -- 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