[
https://issues.apache.org/jira/browse/TEZ-2300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14720337#comment-14720337
]
Bikas Saha commented on TEZ-2300:
---------------------------------
The first config setting probably needs to be removed since the specific tests
are setting it for themselves?
{code} conf.setBoolean(TezConfiguration.TEZ_IGNORE_LIB_URIS, true);
conf.setBoolean(TezConfiguration.TEZ_AM_SESSION_MODE, isSession);
+ conf.setBoolean(TezConfiguration.TEZ_CLIENT_ASYNCHRONOUS_STOP, false);
+ conf.setLong(TezConfiguration.TEZ_CLIENT_HARD_KILL_TIMEOUT_MS,
HARD_KILL_TIMEOUT);{code}
> 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)
