Return-Path: 
 <yarn-issues-return-72081-apmail-hadoop-yarn-issues-archive=hadoop.apache.org@hadoop.apache.org>
X-Original-To: apmail-hadoop-yarn-issues-archive@minotaur.apache.org
Delivered-To: apmail-hadoop-yarn-issues-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 33A4218137
	for <apmail-hadoop-yarn-issues-archive@minotaur.apache.org>;
 Fri, 23 Oct 2015 01:07:28 +0000 (UTC)
Received: (qmail 84210 invoked by uid 500); 23 Oct 2015 01:07:28 -0000
Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org
Received: (qmail 84168 invoked by uid 500); 23 Oct 2015 01:07:28 -0000
Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:yarn-issues-help@hadoop.apache.org>
List-Unsubscribe: <mailto:yarn-issues-unsubscribe@hadoop.apache.org>
List-Post: <mailto:yarn-issues@hadoop.apache.org>
List-Id: <yarn-issues.hadoop.apache.org>
Reply-To: yarn-issues@hadoop.apache.org
Delivered-To: mailing list yarn-issues@hadoop.apache.org
Received: (qmail 83951 invoked by uid 99); 23 Oct 2015 01:07:27 -0000
Received: from arcas.apache.org (HELO arcas) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 23 Oct 2015 01:07:27 +0000
Received: from arcas.apache.org (localhost [127.0.0.1])
	by arcas (Postfix) with ESMTP id BA1DE2C1F6D
	for <yarn-issues@hadoop.apache.org>; Fri, 23 Oct 2015 01:07:27 +0000 (UTC)
Date: Fri, 23 Oct 2015 01:07:27 +0000 (UTC)
From: "Jun Gong (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12904224.1444665978000.35157.1445562447760@Atlassian.JIRA>
In-Reply-To: <JIRA.12904224.1444665978000@Atlassian.JIRA>
References: <JIRA.12904224.1444665978000@Atlassian.JIRA>
 <JIRA.12904224.1444665978433@arcas>
Subject: [jira] [Commented] (YARN-4256) YARN fair scheduler vcores with
 decimal values
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-4256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14970225#comment-14970225 ] 

Jun Gong commented on YARN-4256:
--------------------------------

Thanks [~zxu] for the review and commit!

> YARN fair scheduler vcores with decimal values
> ----------------------------------------------
>
>                 Key: YARN-4256
>                 URL: https://issues.apache.org/jira/browse/YARN-4256
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: fairscheduler
>    Affects Versions: 2.7.1
>            Reporter: Prabhu Joseph
>            Assignee: Jun Gong
>            Priority: Minor
>             Fix For: 2.8.0
>
>         Attachments: YARN-4256.001.patch, YARN-4256.002.patch
>
>
> When the queue with vcores is in decimal value, the value after the decimal point is taken as vcores by FairScheduler.
> For the below queue,
>         <minResources>20000 mb,20 vcores,20.25 disks</minResources>
>         <maxResources>30000 mb,40.2 vcores,30.25 disks</maxResources>
> When many applications submitted  parallely into queue, all were in PENDING state as the vcores is taken as 2 skipping the value 40.
> The code FairSchedulerConfiguration.java to Pattern match the vcores has to be improved in such a way either throw AllocationConfigurationException("Missing resource") or consider the value before decimal.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)