hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tsuyoshi OZAWA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-2052) ContainerId creation after work preserving restart is broken
Date Wed, 14 May 2014 17:09:18 GMT

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

Tsuyoshi OZAWA commented on YARN-2052:
--------------------------------------

{quote}
 e.g. container_XXX_1000 after epoch 1. 
{quote}

This approach can be compatible change. ConverterUtils.toContainerId(containerIdStr) works
without any changes if the container id with the epoch is under Integer.MAX_VALUE. What's
happens if id overflows? Maybe container id collision occurs. If we can handle it correctly,
this approach is simple and good choice. I'll take a moment about this approach.

> ContainerId creation after work preserving restart is broken
> ------------------------------------------------------------
>
>                 Key: YARN-2052
>                 URL: https://issues.apache.org/jira/browse/YARN-2052
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: resourcemanager
>            Reporter: Tsuyoshi OZAWA
>
> Container ids are made unique by using the app identifier and appending a monotonically
increasing sequence number to it. Since container creation is a high churn activity the RM
does not store the sequence number per app. So after restart it does not know what the new
sequence number should be for new allocations.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message