[
https://issues.apache.org/jira/browse/TEZ-808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14977737#comment-14977737
]
Bikas Saha commented on TEZ-808:
--------------------------------
Changed to volatile boolean.
Yes. LLAP scenarios decrease many configs for low latency. If a query finishes
in 2s then I presume most tasks must finish and RPC back pretty fast.
We cannot change the task heartbeat interval since that is at the AM service
level while the progress timeout can be per vertex. Even if were not per
vertex, it can be per DAG and hence cannot change the per AM shared task
communicator service. Unfortunate side effect of having configs is this kind of
manual intervention. I can add to the documentation to mention that progress
timeout should be greater than task ping timeout.
> Handle task attempts that are not making progress
> -------------------------------------------------
>
> Key: TEZ-808
> URL: https://issues.apache.org/jira/browse/TEZ-808
> Project: Apache Tez
> Issue Type: Sub-task
> Reporter: Bikas Saha
> Assignee: Bikas Saha
> Attachments: TEZ-808.1.patch
>
>
> If a task attempt is not making progress then it may cause the job to hang.
> We may want to kill and restart the attempt. With speculation support and
> free resources we may want to run another version in parallel.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
