hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-1630) Introduce timeout for async polling operations in YarnClientImpl
Date Wed, 29 Jan 2014 11:14:12 GMT

    [ https://issues.apache.org/jira/browse/YARN-1630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13885238#comment-13885238
] 

Hudson commented on YARN-1630:
------------------------------

SUCCESS: Integrated in Hadoop-Yarn-trunk #465 (See [https://builds.apache.org/job/Hadoop-Yarn-trunk/465/])
YARN-1630. Introduce timeout for async polling operations in YarnClientImpl (Aditya Acharya
via Sandy Ryza) (sandy: http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1562289)
* /hadoop/common/trunk/hadoop-yarn-project/CHANGES.txt
* /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api/src/main/java/org/apache/hadoop/yarn/conf/YarnConfiguration.java
* /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-client/src/main/java/org/apache/hadoop/yarn/client/api/impl/YarnClientImpl.java
* /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-client/src/test/java/org/apache/hadoop/yarn/client/api/impl/TestYarnClient.java


> Introduce timeout for async polling operations in YarnClientImpl
> ----------------------------------------------------------------
>
>                 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
>             Fix For: 2.3.0
>
>         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)

Mime
View raw message