[
https://issues.apache.org/jira/browse/YARN-743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13672162#comment-13672162
]
Bikas Saha commented on YARN-743:
---------------------------------
Both approaches seem fine to me. The current approach was chosen because it
forces the user to set progress every time an allocation request is made. This
is good because allocate() doubles up as a heartbeat and the RM expects the app
to show progress or else the RM might terminate the app. Forcing the user to
specify progress on every allocate() is useful IMO because it ensures that
progress updates are made. Of course, a user can choose to send the same value
every time but that cannot be helped in any way. Javadoc only helps if the user
reads javadoc for all methods.
> AMRMClient should have a separate setProgress instead of sending progress as
> part of allocate
> ---------------------------------------------------------------------------------------------
>
> Key: YARN-743
> URL: https://issues.apache.org/jira/browse/YARN-743
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Vinod Kumar Vavilapalli
> Assignee: Vinod Kumar Vavilapalli
>
> Progress updates are independent of allocations and so should be set
> explicitly.
--
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
