[
https://issues.apache.org/jira/browse/YARN-417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13606087#comment-13606087
]
Sandy Ryza commented on YARN-417:
---------------------------------
bq. I was actually talking about the allocate() call in the heartbeat thread
which can happen between client.stop() and heartbeathandler.join().
My point was that unregisterApplicationMaster would stop the heartbeater before
we had a chance to encounter this. But I just looked again and realized that I
had incorrectly assumed unregisterApplicationMaster was synchronized, so I'll
address this in an upcoming patch. Sorry for the confusion.
bq. It would actually make the test flaky.
Oops, you're right; I'm not sure what I was thinking.
bq. For good or bad, app progress is sent on every allocate call. Which means
that the app must keep setting a new value of progress on a periodic interval
(that is related to the allocated heartbeat interval).
What I'm confused about is how the second sentence follows from the first.
Currently, the AMRMClientAsync stores the progress it's given and keeps sending
it with each heartbeat, until the app calls setProgress updates it with a new
progress, at which point it will keep sending that one instead.
> 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-4.patch,
> YARN-417-4.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
