[
https://issues.apache.org/jira/browse/TEZ-3296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15334623#comment-15334623
]
Bikas Saha edited comment on TEZ-3296 at 6/16/16 8:29 PM:
----------------------------------------------------------
Ah. Looks like a result of using priority as a key for unique requests vs using
it a just priority. Sigh! /cc [~vinodkv] [~wangda]
was (Author: bikassaha):
Ah. Looks like a result of using priority as a key for unique requests vs using
it a just priority.
> Tez job can hang if two vertices at the same root distance have different
> task requirements
> -------------------------------------------------------------------------------------------
>
> Key: TEZ-3296
> URL: https://issues.apache.org/jira/browse/TEZ-3296
> Project: Apache Tez
> Issue Type: Bug
> Affects Versions: 0.7.1
> Reporter: Jason Lowe
> Assignee: Jason Lowe
> Priority: Critical
> Fix For: 0.7.2, 0.9.0, 0.8.4
>
> Attachments: TEZ-3296.001.patch
>
>
> When two vertices have the same distance from the root Tez will schedule
> containers with the same priority. However those vertices could have
> different task requirements and therefore different capabilities. As
> documented in YARN-314, YARN currently doesn't support requests for multiple
> sizes at the same priority. In practice this leads to one vertex allocation
> requests clobbering the other, and that can result in a situation where the
> Tez AM is waiting on containers it will never receive from the RM.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
