Return-Path: X-Original-To: apmail-reef-dev-archive@minotaur.apache.org Delivered-To: apmail-reef-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 78D0C176B2 for ; Wed, 2 Dec 2015 06:16:11 +0000 (UTC) Received: (qmail 93627 invoked by uid 500); 2 Dec 2015 06:16:11 -0000 Delivered-To: apmail-reef-dev-archive@reef.apache.org Received: (qmail 93556 invoked by uid 500); 2 Dec 2015 06:16:11 -0000 Mailing-List: contact dev-help@reef.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@reef.apache.org Delivered-To: mailing list dev@reef.apache.org Received: (qmail 93531 invoked by uid 99); 2 Dec 2015 06:16:11 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 02 Dec 2015 06:16:11 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 1C1282C1F7C for ; Wed, 2 Dec 2015 06:16:11 +0000 (UTC) Date: Wed, 2 Dec 2015 06:16:11 +0000 (UTC) From: "John Yang (JIRA)" To: dev@reef.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Comment Edited] (REEF-1014) Expose hard Evaluator preemption on YARN 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/REEF-1014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15035343#comment-15035343 ] John Yang edited comment on REEF-1014 at 12/2/15 6:16 AM: ---------------------------------------------------------- I'd like {{PreemptedEvaluator}} to cover only hard preemption, and expose soft preemption separately, for example as {{PreemptionMessage}}. The main reason is that soft preemption is technically not a preemption, but rather a hint. So it'd be better not to mix these two concepts in a single handler type. I think exposing soft preemption can be discussed/addressed in a separate JRIA issue. was (Author: johnyangk): I'd like {{PreemptedEvaluator}] to cover only hard preemption, and expose soft preemption separately, for example as {{PreemptionMessage}}. The main reason is that soft preemption is technically not a preemption, but rather a hint. So it'd be better not to mix these two concepts in a single handler type. I think exposing soft preemption can be discussed/addressed in a separate JRIA issue. > Expose hard Evaluator preemption on YARN > ---------------------------------------- > > Key: REEF-1014 > URL: https://issues.apache.org/jira/browse/REEF-1014 > Project: REEF > Issue Type: Sub-task > Components: REEF Driver, REEF Runtime YARN > Reporter: John Yang > Assignee: John Yang > > Expose to REEF users hard Evaluator preemption on YARN. We can leverage {{ContainerExitStatus.PREEMPTED}} YARN RM gives to REEF Driver. -- This message was sent by Atlassian JIRA (v6.3.4#6332)