hadoop-yarn-issues mailing list archives

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

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

Hitesh Shah commented on YARN-226:
----------------------------------

@Sid, nevermind - reservations could effectively increment the id and never assign 1 to anything.
@Eli, this will occur on clusters when the AM resource ask is greater than a single slot and
it requires multiple scheduling cycles before a large free slot is available to launch the
AM.
 
                
> 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