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 94F47200C3B for ; Sat, 11 Feb 2017 01:45:45 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 926B4160B5C; Sat, 11 Feb 2017 00:45:45 +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 D9576160B69 for ; Sat, 11 Feb 2017 01:45:44 +0100 (CET) Received: (qmail 30558 invoked by uid 500); 11 Feb 2017 00:45:44 -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 30547 invoked by uid 99); 11 Feb 2017 00:45:44 -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; Sat, 11 Feb 2017 00:45:44 +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 7EE7F1A02E3 for ; Sat, 11 Feb 2017 00:45:43 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -1.999 X-Spam-Level: X-Spam-Status: No, score=-1.999 tagged_above=-999 required=6.31 tests=[KAM_LAZY_DOMAIN_SECURITY=1, RP_MATCHES_RCVD=-2.999] 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 4W5UZ2PRGFPt for ; Sat, 11 Feb 2017 00:45:42 +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 6C0B95F342 for ; Sat, 11 Feb 2017 00:45:42 +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 EA9A7E00D3 for ; Sat, 11 Feb 2017 00:45:41 +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 A91D621D64 for ; Sat, 11 Feb 2017 00:45:41 +0000 (UTC) Date: Sat, 11 Feb 2017 00:45:41 +0000 (UTC) From: "Yufei Gu (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (YARN-6175) Negative vcore for resource needed to preempt MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Sat, 11 Feb 2017 00:45:45 -0000 [ https://issues.apache.org/jira/browse/YARN-6175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yufei Gu updated YARN-6175: --------------------------- Description: Both old preemption code (2.8 and before) and new preemption code could have negative vcores while calculating resources needed to preempt. For old preemption, you can find following messages in RM logs: {code} Should preempt {code} The related code is in method {{resourceDeficit()}}. For new preemption code, there are no messages in RM logs, the related code is in method {{fairShareStarvation()}}. The negative value isn't only a display issue, but also may cause missing necessary preemption. was: Both old preemption code (2.8 and before) and new preemption code could have negative vcores while calculating resources needed to preempt. For old preemption code would has these message: {code} Should preempt {code} The related code is in method {{resourceDeficit()}}. For new preemption code, the related code is in method {{fairShareStarvation()}}. The negative value isn't only a display issue, but also may cause missing necessary preemption. > Negative vcore for resource needed to preempt > --------------------------------------------- > > Key: YARN-6175 > URL: https://issues.apache.org/jira/browse/YARN-6175 > Project: Hadoop YARN > Issue Type: Bug > Components: fairscheduler > Affects Versions: 2.8.0, 3.0.0-alpha2 > Reporter: Yufei Gu > Assignee: Yufei Gu > > Both old preemption code (2.8 and before) and new preemption code could have negative vcores while calculating resources needed to preempt. > For old preemption, you can find following messages in RM logs: > {code} > Should preempt > {code} > The related code is in method {{resourceDeficit()}}. > For new preemption code, there are no messages in RM logs, the related code is in method {{fairShareStarvation()}}. > The negative value isn't only a display issue, but also may cause missing necessary preemption. -- This message was sent by Atlassian JIRA (v6.3.15#6346) --------------------------------------------------------------------- To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org For additional commands, e-mail: yarn-issues-help@hadoop.apache.org