[
https://issues.apache.org/jira/browse/HIVE-10280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15218475#comment-15218475
]
Sergey Shelukhin edited comment on HIVE-10280 at 3/30/16 6:05 PM:
------------------------------------------------------------------
The code looks reasonable... the logic though, would it mean one temp failure
will make AM discard all tasks on the node?
I also assume it's safe to mark running tasks as killed from AM perspective
(wrt potential future events from them, etc.); -however should we try to send
kill to them (and ignore the failures) so they don't hog resources- actually it
may be a good idea to send a kill if we received a status update from some task
that we declared dead.
was (Author: sershe):
The code looks reasonable... the logic though, would it mean one temp failure
will make AM discard all tasks on the node?
I also assume it's safe to mark running tasks as killed from AM perspective
(wrt potential future events from them, etc.); however should we try to send
kill to them (and ignore the failures) so they don't hog resources?
> LLAP: Handle errors while sending source state updates to the daemons
> ---------------------------------------------------------------------
>
> Key: HIVE-10280
> URL: https://issues.apache.org/jira/browse/HIVE-10280
> Project: Hive
> Issue Type: Sub-task
> Components: llap
> Reporter: Siddharth Seth
> Assignee: Siddharth Seth
> Attachments: HIVE-10280.1.patch
>
>
> Will likely be handled as marking the node as bad. May need a retry policy in
> place though before marking a node bad to handle temporary network glitches.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
