hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "sandflee (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-3387) Previous AM's container complete message couldn't pass to current am if am restarted and rm changed
Date Sat, 25 Apr 2015 00:02:43 GMT

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

sandflee commented on YARN-3387:
--------------------------------

Thanks He Jian and Anubhav

> Previous AM's container complete message couldn't pass to current am if am restarted
and rm changed
> ---------------------------------------------------------------------------------------------------
>
>                 Key: YARN-3387
>                 URL: https://issues.apache.org/jira/browse/YARN-3387
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: resourcemanager
>    Affects Versions: 2.6.0
>            Reporter: sandflee
>            Assignee: sandflee
>            Priority: Critical
>              Labels: patch
>             Fix For: 2.8.0
>
>         Attachments: YARN-3387.001.patch, YARN-3387.002.patch
>
>
> suppose am work preserving and rm ha is enabled.
> container complete message is passed to appattemt.justFinishedContainers in rm。in normal
situation,all attempt in one app shares the same justFinishedContainers, but when rm changed,
every attempt has it's own justFinishedContainers, so in situations below, container complete
message couldn't passed to am:
> 1, am restart
> 2, rm changes
> 3, container launched by first am completes
> container complete message will be passed to appAttempt1 not appAttempt2, but am pull
finished containers from appAttempt2 (currentAppAttempt)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message