[
https://issues.apache.org/jira/browse/YARN-1630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13883614#comment-13883614
]
Hadoop QA commented on YARN-1630:
---------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12625490/diff-1.txt
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The following test timeouts occurred in
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-client:
org.apache.hadoop.yarn.client.api.impl.TestNMClient
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/2945//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/2945//console
This message is automatically generated.
> Unbounded waiting for response in YarnClientImpl.java causes thread to hang
> forever
> -----------------------------------------------------------------------------------
>
> Key: YARN-1630
> URL: https://issues.apache.org/jira/browse/YARN-1630
> Project: Hadoop YARN
> Issue Type: Bug
> Components: client
> Affects Versions: 2.2.0
> Reporter: Aditya Acharya
> Assignee: Aditya Acharya
> Attachments: diff-1.txt, diff.txt
>
>
> I ran an MR2 application that would have been long running, and killed it
> programmatically using a YarnClient. The app was killed, but the client hung
> forever. The message that I saw, which spammed the logs, was "Watiting for
> application application_1389036507624_0018 to be killed."
> The RM log indicated that the app had indeed transitioned from RUNNING to
> KILLED, but for some reason future responses to the RPC to kill the
> application did not indicate that the app had been terminated.
> I tracked this down to YarnClientImpl.java, and though I was unable to
> reproduce the bug, I wrote a patch to introduce a bound on the number of
> times that YarnClientImpl retries the RPC before giving up.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
