[
https://issues.apache.org/jira/browse/YARN-417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13595378#comment-13595378
]
Hitesh Shah commented on YARN-417:
----------------------------------
@Bikas, @Chris, is there a reason as to why all information needs to be sent
back via callbacks? Could the AsyncAMRMClient "cache" the last known available
resources information obtained from the RM and provide a function to access it
as needed. Assuming the application master has been written to handle events,
it is very likely that when deciding what to ask the next time around, it could
simply query the current available resources and make a decision based on that
info.
+1 to Bikas's comment on separate callbacks for the allocation and completion
sets - complex AMs may find that the order of callbacks create problems as each
set will be handled separately without an overall picture. For simpler AMs,
this may suffice which I am assuming is the goal here.
> 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-1.patch, YARN-417-2.patch, YARN-417-3.patch, 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
