You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@tez.apache.org by "Chang Li (JIRA)" <ji...@apache.org> on 2015/06/02 17:14:18 UTC
[jira] [Comment Edited] (TEZ-2300) TezClient.stop() takes a lot of
time or does not work sometimes
[ https://issues.apache.org/jira/browse/TEZ-2300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14569247#comment-14569247 ]
Chang Li edited comment on TEZ-2300 at 6/2/15 3:13 PM:
-------------------------------------------------------
[~rohini], [~hitesh], should I file two separate jiras as sub tasks to address the TezClient.stop() and yarn kill issues which Rohini point out?
was (Author: lichangleo):
[~rohini], [~hitesh], should I file two separate jiras as sub tasks to address the TezClient.stop() and yarn kill issues as Rohini point out?
> TezClient.stop() takes a lot of time or does not work sometimes
> ---------------------------------------------------------------
>
> Key: TEZ-2300
> URL: https://issues.apache.org/jira/browse/TEZ-2300
> Project: Apache Tez
> Issue Type: Bug
> Reporter: Rohini Palaniswamy
> Attachments: syslog_dag_1428329756093_325099_1_post
>
>
> Noticed this with a couple of pig scripts which were not behaving well (AM close to OOM, etc) and even with some that were running fine. Pig calls Tezclient.stop() in shutdown hook. Ctrl+C to the pig script either exits immediately or is hung. In both cases it either takes a long time for the yarn application to go to KILLED state. Many times I just end up calling yarn application -kill separately after waiting for 5 mins or more for it to get killed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)