[
https://issues.apache.org/jira/browse/AURORA-1149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15223330#comment-15223330
]
Stephan Erb commented on AURORA-1149:
-------------------------------------
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)
