[
https://issues.apache.org/jira/browse/YARN-1954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13975658#comment-13975658
]
Tsuyoshi OZAWA commented on YARN-1954:
--------------------------------------
Thank you for the comment, [~zjshen]. Updated a patch:
1. Changed APIs to wait infinitely.
2. Added log in main loop. I concerned that it can be overhead to log too much.
Should we add logging interval as a new parameter?
3. Created YARN-1967 to address this issue.
4. Added AMRMClient support.
5. Added methods to test waitFor() in another methods.
> 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
>
>
> 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)
