[
https://issues.apache.org/jira/browse/TEZ-2964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15029223#comment-15029223
]
Siddharth Seth commented on TEZ-2964:
-------------------------------------
[~gopalv] - do you have the AM logs by any chance ? and how often does this
happen.
>From walking through the code, I don't see how this happens. The fact that
>once the first attempt fails - every subsequent one runs into the same issue
>is interesting though.
> Tez AMScheduler - assign to unallocated container
> -------------------------------------------------
>
> Key: TEZ-2964
> URL: https://issues.apache.org/jira/browse/TEZ-2964
> Project: Apache Tez
> Issue Type: Bug
> Affects Versions: 0.8.2
> Reporter: Gopal V
> Assignee: Siddharth Seth
>
> Under high concurrency, the pre-emption causes tez AppMaster to die.
> {code}
> vertexId=vertex_1448429572030_0467_1_02, diagnostics=[Task failed,
> taskId=task_1448429572030_0467_1_02_000000, diagnostics=[TaskAttempt 0
> killed, TaskAttempt 1 killed, TaskAttempt 2 killed, TaskAttempt 3 killed,
> TaskAttempt 4 killed, TaskAttempt 5 killed, TaskAttempt 6 killed, TaskAttempt
> 7 killed, TaskAttempt 8 killed, TaskAttempt 9 killed, TaskAttempt 10 killed,
> TaskAttempt 11 killed, TaskAttempt 12 failed, info=[AMScheduler Error:
> TaskAttempt allocated to unlaunched container:
> container_222212222_0467_01_002488], TaskAttempt 13 failed, info=[AMScheduler
> Error: TaskAttempt allocated to unlaunched container:
> container_222212222_0467_01_002489], TaskAttempt 14 failed, info=[AMScheduler
> Error: TaskAttempt allocated to unlaunched container:
> container_222212222_0467_01_002490], TaskAttempt 15 failed, info=[AMScheduler
> Error: TaskAttempt allocated to unlaunched container:
> container_222212222_0467_01_002491]],
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
