hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Zhijie Shen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-1954) Add waitFor to AMRMClient(Async)
Date Mon, 04 Aug 2014 17:58:14 GMT

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

Zhijie Shen commented on YARN-1954:
-----------------------------------

My concern is that if users want a even larger checkEveryMillis, he may not get it, and the
log is actually recorded at 60000ms silently. If 60000ms is the interval cap, we should somehow
let users know.

> Add waitFor to AMRMClient(Async)
> --------------------------------
>
>                 Key: YARN-1954
>                 URL: https://issues.apache.org/jira/browse/YARN-1954
>             Project: Hadoop YARN
>          Issue Type: New Feature
>          Components: client
>    Affects Versions: 3.0.0, 2.4.0
>            Reporter: Zhijie Shen
>            Assignee: Tsuyoshi OZAWA
>         Attachments: YARN-1954.1.patch, YARN-1954.2.patch, YARN-1954.3.patch, YARN-1954.4.patch,
YARN-1954.4.patch
>
>
> Recently, I saw some use cases of AMRMClient(Async). The painful thing is that the main
non-daemon thread has to sit in a dummy loop to prevent AM process exiting before all the
tasks are done, while unregistration is triggered on a separate another daemon thread by callback
methods (in particular when using AMRMClientAsync). IMHO, it should be beneficial to add a
waitFor method to AMRMClient(Async) to block the AM until unregistration or user supplied
check point, such that users don't need to write the loop themselves.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message