[
https://issues.apache.org/jira/browse/YARN-417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13589177#comment-13589177
]
Sandy Ryza commented on YARN-417:
---------------------------------
That's sounds right Chris. Will include that in the class's doc.
I've thought a little more about the ContainerCompletionReason, and I'm not
sure it's necessary, as there are already constants in YarnConfiguration for
the special exit codes, and there are only two, ABORTED_CONTAINER_EXIT_STATUS
and DISK_FAILED. As these don't really have to do with configuration, it might
make sense to move them to a ContainerExitCodes class, and just point to that
class in the doc for ContainerStatus#getExitCode and
CallbackHandler#onContainersCompleted
> Add a poller that allows the AM to receive notifications when it is assigned
> containers
> ---------------------------------------------------------------------------------------
>
> Key: YARN-417
> URL: https://issues.apache.org/jira/browse/YARN-417
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: api, applications
> Affects Versions: 2.0.3-alpha
> Reporter: Sandy Ryza
> Assignee: Sandy Ryza
> Attachments: AMRMClientAsync-1.java, AMRMClientAsync.java,
> YARN-417.patch, YarnAppMaster.java, YarnAppMasterListener.java
>
>
> Writing AMs would be easier for some if they did not have to handle
> heartbeating to the RM on their own.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
