You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@tez.apache.org by "wei (Jira)" <ji...@apache.org> on 2021/07/05 16:06:00 UTC

[jira] [Commented] (TEZ-4317) Tez job can hang if new allocated container released because of speculative attempts avoid running on the same node

    [ https://issues.apache.org/jira/browse/TEZ-4317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17374916#comment-17374916 ] 

wei commented on TEZ-4317:
--------------------------

ping [~yingdachen] [~Chyler]

> Tez job can hang if new allocated container released because of speculative attempts avoid running on the same node
> -------------------------------------------------------------------------------------------------------------------
>
>                 Key: TEZ-4317
>                 URL: https://issues.apache.org/jira/browse/TEZ-4317
>             Project: Apache Tez
>          Issue Type: Bug
>    Affects Versions: 0.9.2
>            Reporter: wei
>            Priority: Major
>
> Assuming that a task attempt is running, eg: TA01.
> Then one speculated task attempt scheduled with allocated container same host with TA01, this new allocated container will be released because of [TEZ-4042|https://issues.apache.org/jira/browse/TEZ-4042] and no new resource request added.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)