You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@tez.apache.org by "Jeff Zhang (JIRA)" <ji...@apache.org> on 2015/09/01 10:18:46 UTC
[jira] [Commented] (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=14724957#comment-14724957 ]
Jeff Zhang commented on TEZ-2300:
---------------------------------
Findbug warning caused by this ticket. [~jeagles] Could you help check that.
{noformat}
Code Warning
SWL org.apache.tez.client.TezClient.stop() calls Thread.sleep() with a lock held
{noformat}
> 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
> Assignee: Jonathan Eagles
> Fix For: 0.7.1
>
> Attachments: TEZ-2300.1.patch, TEZ-2300.10.patch, TEZ-2300.2.patch, TEZ-2300.3.patch, TEZ-2300.4.patch, TEZ-2300.5.patch, TEZ-2300.6.patch, TEZ-2300.7.patch, TEZ-2300.8.patch, TEZ-2300.9.patch, 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)