Rohith commented on YARN-1366:

bq. Rohith let me know if you mind if we add these as well to YARN-1365.

bq. If the AMRMClientAsync is not doing this then we should fix it.
we need not to fix this. It is handled by setting keepRunning flag to false.

bq. allow finishApplicationMaster to succeed when responseMap is set to -1 (ie 
not yet registered but known to be last). 
It would require additional state transition for. 
        RMAppAttemptImpl : LAUNCHED -> 
EnumSet.of(RMAppAttemptState.FINAL_SAVING, RMAppAttemptState.FINISHED)
        RMAppImpl             : ACCEPTED -> FINAL_SAVING

>From above overall discussions, on resync existing approach will be used 
>istead of going with new API.Please let me know anyone has concern on this?

> 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
>            Assignee: Rohith
>         Attachments: YARN-1366.1.patch, YARN-1366.2.patch, YARN-1366.patch, 
> YARN-1366.prototype.patch, YARN-1366.prototype.patch
> 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

Reply via email to