You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@aurora.apache.org by "David McLaughlin (JIRA)" <ji...@apache.org> on 2018/01/25 18:23:00 UTC
[jira] [Assigned] (AURORA-1965) LaunchException needs transient
task timeout for reschedule
[ https://issues.apache.org/jira/browse/AURORA-1965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David McLaughlin reassigned AURORA-1965:
----------------------------------------
Assignee: David McLaughlin
> LaunchException needs transient task timeout for reschedule
> -----------------------------------------------------------
>
> Key: AURORA-1965
> URL: https://issues.apache.org/jira/browse/AURORA-1965
> Project: Aurora
> Issue Type: Bug
> Reporter: Santhosh Kumar Shanmugham
> Assignee: David McLaughlin
> Priority: Minor
>
> In {{TaskAssignerImpl}} a {{LaunchException}} either due to race-condition for grabbing {{Offer}} or Scheduler Driver {{acceptOffers}} failure will result in the task being help up in {{ASSIGNED}} state, until transient task timeout kicks in to move the task to LOST, resulting in a reschedule.
> [https://github.com/apache/aurora/blob/dbe71374399d86d77baa35efbeca4fffa34f380e/src/main/java/org/apache/aurora/scheduler/scheduling/TaskAssignerImpl.java#L135]
> The impact of this is minimal due to fact that multiple conditions need to align for this situation to happen.
> This happens since the call to {{changeState}} fails since the supplied current state (PENDING) in the method call is different from the actual state of the task (ASSIGNED).
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)