[
https://issues.apache.org/jira/browse/TEZ-2300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14488203#comment-14488203
]
Rohini Palaniswamy edited comment on TEZ-2300 at 4/9/15 8:26 PM:
-----------------------------------------------------------------
Recently, it was from too many job runs for issues TEZ-776 is trying to
address. I haven't kept track and the job logs are huge to dig and find out
what I did to which job. Will get some with future runs.
was (Author: rohini):
Recently, it was from too many job runs for issues addressed TEZ-776. I haven't
kept track and the job logs are huge to dig and find out what I did to which
job. Will get some with future runs.
> 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
>
> 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)
