[
https://issues.apache.org/jira/browse/YARN-308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13544245#comment-13544245
]
Sandy Ryza commented on YARN-308:
---------------------------------
For pure absolute, we would only need to send the full list for the rare
heartbeats where we want to make a change to an application's request. An
empty list of asks would indicate no change, as it does currently. We would
have to do something special if an AM wants to indicate cancelling all tasks,
but it wouldn't be any more complex than what's required now. A
ResourceRequest contains a resource capability and a number of containers, so
1000 tasks would only take more processing than one task if they had 1000
different locations or priorities.
> Improve documentation about what "asks" means in AMRMProtocol
> -------------------------------------------------------------
>
> Key: YARN-308
> URL: https://issues.apache.org/jira/browse/YARN-308
> Project: Hadoop YARN
> Issue Type: Bug
> Components: api, resourcemanager
> Affects Versions: 2.0.2-alpha
> Reporter: Sandy Ryza
> Assignee: Sandy Ryza
> Fix For: 2.0.3-alpha
>
>
> It's unclear to me from reading the javadoc exactly what "asks" means when
> the AM sends a heartbeat to the RM. Is the AM supposed to send a list of all
> resources that it is waiting for? Or just inform the RM about new ones that
> it wants?
--
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