[
https://issues.apache.org/jira/browse/YARN-1366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13809755#comment-13809755
]
Bikas Saha commented on YARN-1366:
----------------------------------
Yes. the lastResponseId needs to reset to 0 and all the client side data like
asks, blacklists etc should be sent in full to the RM.
The AMRMToken for the attempt is saved and restored. So the existing attempt
will be able to reconnect to the restarted RM. This currently works.
> ApplicationMasterService should Resync with the AM upon allocate call after
> restart
> -----------------------------------------------------------------------------------
>
> Key: YARN-1366
> URL: https://issues.apache.org/jira/browse/YARN-1366
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: resourcemanager
> Reporter: Bikas Saha
>
> The ApplicationMasterService currently sends a resync response to which the
> AM responds by shutting down. The AM behavior is expected to change to
> calling resyncing with the RM. Resync means resetting the allocate RPC
> sequence number to 0 and the AM should send its entire outstanding request to
> the RM. Note that if the AM is making its first allocate call to the RM then
> things should proceed like normal without needing a resync. The RM will
> return all containers that have completed since the RM last synced with the
> AM. Some container completions may be reported more than once.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
