hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eli Reisman (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-226) Log aggregation should not assume an AppMaster will have containerId 1
Date Fri, 15 Mar 2013 17:06:13 GMT

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

Eli Reisman commented on YARN-226:
----------------------------------

Hmm. It would not be impossible to ask for one container, launch it, then
the rest of the graph tasks so that first one can be set up to know its
first. I think the whole "task 0" thing is old in Giraph and could be
handled another way by now. I will look into it. It didn't make a lot of
sense when that approach worked to start with, but it worked right away so
I went with it ;)





                
> Log aggregation should not assume an AppMaster will have containerId 1
> ----------------------------------------------------------------------
>
>                 Key: YARN-226
>                 URL: https://issues.apache.org/jira/browse/YARN-226
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>            Reporter: Siddharth Seth
>
> In case of reservcations, etc - AppMasters may not get container id 1. We likely need
additional info in the CLC / tokens indicating whether a container is an AM or not.

--
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

Mime
View raw message