hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Li Lu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-2354) DistributedShell may allocate more containers than client specified after it restarts
Date Wed, 30 Jul 2014 03:48:38 GMT

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

Li Lu commented on YARN-2354:
-----------------------------

Thanks [~jianhe]. In the second time I think the only problem left is the persistent one,
but unrelated to this patch. 

> DistributedShell may allocate more containers than client specified after it restarts
> -------------------------------------------------------------------------------------
>
>                 Key: YARN-2354
>                 URL: https://issues.apache.org/jira/browse/YARN-2354
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>            Reporter: Jian He
>            Assignee: Li Lu
>         Attachments: YARN-2354-072514.patch, YARN-2354-072814.patch, YARN-2354-072914.patch
>
>
> To reproduce, run distributed shell with -num_containers option,
> In ApplicationMaster.java, the following code has some issue.
> {code}
>   int numTotalContainersToRequest =
>         numTotalContainers - previousAMRunningContainers.size();
>     for (int i = 0; i < numTotalContainersToRequest; ++i) {
>       ContainerRequest containerAsk = setupContainerAskForRM();
>       amRMClient.addContainerRequest(containerAsk);
>     }
>     numRequestedContainers.set(numTotalContainersToRequest);
> {code}
>  numRequestedContainers doesn't account for previous AM's requested containers. so numRequestedContainers
should be set to numTotalContainers



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

Mime
View raw message