Return-Path: 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 69E8F18D2A for ; Wed, 16 Dec 2015 14:27:47 +0000 (UTC) Received: (qmail 1291 invoked by uid 500); 16 Dec 2015 14:27:46 -0000 Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org Received: (qmail 1234 invoked by uid 500); 16 Dec 2015 14:27:46 -0000 Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: yarn-issues@hadoop.apache.org Delivered-To: mailing list yarn-issues@hadoop.apache.org Received: (qmail 1211 invoked by uid 99); 16 Dec 2015 14:27:46 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 16 Dec 2015 14:27:46 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id A75D32C1F6F for ; Wed, 16 Dec 2015 14:27:46 +0000 (UTC) Date: Wed, 16 Dec 2015 14:27:46 +0000 (UTC) From: "Sunil G (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YARN-4462) Scheduler should prevent certain application from being preempted 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-4462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15060039#comment-15060039 ] Sunil G commented on YARN-4462: ------------------------------- Yes Tao Jie. I understood your scenaruo where cost of one long running application is more. YARN-4108 comes up with this improvement. There will be policies which user can configure to selected app. This will surely cover your case. > Scheduler should prevent certain application from being preempted > ----------------------------------------------------------------- > > Key: YARN-4462 > URL: https://issues.apache.org/jira/browse/YARN-4462 > Project: Hadoop YARN > Issue Type: Improvement > Components: scheduler > Affects Versions: 2.6.0 > Reporter: Tao Jie > > When scheduler preemption is enabled, applications could be preempted if they obtain resource over they should take. > When a mapreduce application is preempted some resource, it just runs slower. However, when the preempted application is a long-run service, such as tomcat running in slider, the service would fail. > So we should have a flag for application to indicate the scheduler that those application should not be preempted. -- This message was sent by Atlassian JIRA (v6.3.4#6332)