[ 
https://issues.apache.org/jira/browse/TEZ-2972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jason Lowe updated TEZ-2972:
----------------------------
    Attachment: TEZ-2972.002.patch

Thanks for the review, Bikas!  I updated the patch to avoid sending the node 
failure events to the containers in the AM node tracker rather than avoiding 
sending the node updates to the node tracker.  I also updated the name of the 
config to be a bit more specific about what's being enabled/disabled rather 
than just all node updates, and the default is to not reschedule tasks.


> Ability for Tez AM to ignore node updates from YARN
> ---------------------------------------------------
>
>                 Key: TEZ-2972
>                 URL: https://issues.apache.org/jira/browse/TEZ-2972
>             Project: Apache Tez
>          Issue Type: Improvement
>            Reporter: Jason Lowe
>            Assignee: Jason Lowe
>         Attachments: TEZ-2972.001.patch, TEZ-2972.002.patch
>
>
> This is similar to MAPREDUCE-6119.  Sometimes reacting to a node update event 
> can cause more harm than good.  For example, an UNHEALTHY node may be able to 
> shuffle just fine.  Therefore obsoleting the output of tasks that ran on that 
> node and re-running them simply adds more overhead to the job with no 
> benefit.  It would be nice to be able to configure Tez to ignore node update 
> events if desired.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to