Return-Path: X-Original-To: apmail-aurora-issues-archive@minotaur.apache.org Delivered-To: apmail-aurora-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 D9FA91937D for ; Sun, 3 Apr 2016 14:44:25 +0000 (UTC) Received: (qmail 6844 invoked by uid 500); 3 Apr 2016 14:44:25 -0000 Delivered-To: apmail-aurora-issues-archive@aurora.apache.org Received: (qmail 6733 invoked by uid 500); 3 Apr 2016 14:44:25 -0000 Mailing-List: contact issues-help@aurora.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@aurora.apache.org Delivered-To: mailing list issues@aurora.apache.org Received: (qmail 6714 invoked by uid 99); 3 Apr 2016 14:44:25 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 03 Apr 2016 14:44:25 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 717C72C1F5A for ; Sun, 3 Apr 2016 14:44:25 +0000 (UTC) Date: Sun, 3 Apr 2016 14:44:25 +0000 (UTC) From: "Stephan Erb (JIRA)" To: issues@aurora.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Comment Edited] (AURORA-1149) Decide the appropriate way to handle TASK_ERROR 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/AURORA-1149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15223330#comment-15223330 ] Stephan Erb edited comment on AURORA-1149 at 4/3/16 2:43 PM: ------------------------------------------------------------- Given that nobody seems to have a problem with retrying [1], can we close this issue? [1] https://github.com/apache/aurora/blob/9ed81a7db58f6a7cb308c8ac6a545705351c8c0e/src/main/java/org/apache/aurora/scheduler/base/Conversions.java#L60 was (Author: stephanerb): Given that nobody seems to have a problem with retrying [1], can we close this issue? [1]https://github.com/apache/aurora/blob/9ed81a7db58f6a7cb308c8ac6a545705351c8c0e/src/main/java/org/apache/aurora/scheduler/base/Conversions.java#L60 > Decide the appropriate way to handle TASK_ERROR > ----------------------------------------------- > > Key: AURORA-1149 > URL: https://issues.apache.org/jira/browse/AURORA-1149 > Project: Aurora > Issue Type: Story > Components: Scheduler, Usability > Reporter: Bill Farner > > This may mean the state machine needs to accommodate this state. The outcome should depend on whether we believe TASK_ERROR is truly permanently fatal, or whether it could represent a transient configuration error in some component (e.g. scheduler, master). If we believe TASK_ERROR is indeed always fatal, this should be a terminal and non-reschedulable state regardless of whether the task is a service. However, if it can be transient, we may still want to try to revive the task to avoid temporary configuration errors from tearing down services. > Personally, i'm leaning towards the retry case. -- This message was sent by Atlassian JIRA (v6.3.4#6332)