[ 
https://issues.apache.org/jira/browse/MAPREDUCE-3162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13124696#comment-13124696
 ] 

Chris Douglas commented on MAPREDUCE-3162:
------------------------------------------

bq. startContainer can be called concurrently from several threads, apparently. 
So one thread can insert the ApplicationImpl in the concurrent applications 
map, then another thread can send the INIT_CONTAINER event before the 
INIT_APPLICATION event has been sent.

That was the intent. It should also be legal for the NM to clean up application 
state, given a richer set of semantics for the intermediate output specifying 
retention. Then one would have to re-init the application to start containers 
there. More of the init used to be per-application, before changing the 
localization to be per-container. It's not doing much now, but it's cheap.
                
> Separate application-init and container-init event types in NM's 
> ApplicationImpl FSM
> ------------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-3162
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3162
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>    Affects Versions: 0.23.0
>            Reporter: Todd Lipcon
>            Assignee: Todd Lipcon
>            Priority: Minor
>         Attachments: mr-3162.txt
>
>
> Currently, the ApplicationImpl receives an INIT_APPLICATION event on every 
> container initialization. Only on the first one does it really mean to init 
> the application, whereas all subsequent events are for specific containers. 
> This JIRA is to separate the events into INIT_APPLICATION, sent once and only 
> once per application, and INIT_CONTAINER, which is sent for every container. 
> The first container sends INIT_APPLICATION followed by INIT_CONTAINER.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to