hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-1256) NM silently ignores non-existent service in StartContainerRequest
Date Thu, 03 Oct 2013 20:48:44 GMT

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

Hadoop QA commented on YARN-1256:

{color:green}+1 overall{color}.  Here are the results of testing the latest attachment 
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:green}+1 tests included{color}.  The patch appears to include 2 new or modified
test files.

    {color:green}+1 javac{color}.  The applied patch does not increase the total number of
javac compiler warnings.

    {color:green}+1 javadoc{color}.  The javadoc tool did not generate any warning messages.

    {color:green}+1 eclipse:eclipse{color}.  The patch built with eclipse:eclipse.

    {color:green}+1 findbugs{color}.  The patch does not introduce any new Findbugs (version
1.3.9) warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase the total number
of release audit warnings.

    {color:green}+1 core tests{color}.  The patch passed unit tests in hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager.

    {color:green}+1 contrib tests{color}.  The patch passed contrib unit tests.

Test results: https://builds.apache.org/job/PreCommit-YARN-Build/2078//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/2078//console

This message is automatically generated.

> NM silently ignores non-existent service in StartContainerRequest
> -----------------------------------------------------------------
>                 Key: YARN-1256
>                 URL: https://issues.apache.org/jira/browse/YARN-1256
>             Project: Hadoop YARN
>          Issue Type: Bug
>    Affects Versions: 2.1.1-beta
>            Reporter: Bikas Saha
>            Assignee: Xuan Gong
>            Priority: Critical
>             Fix For: 2.1.2-beta
>         Attachments: YARN-1256.1.patch, YARN-1256.2.patch
> A container can set token service metadata for a service, say shuffle_service. If that
service does not exist then the errors is silently ignored. Later, when the next container
wants to access data written to shuffle_service by the first task, then it fails because the
service does not have the token that was supposed to be set by the first task.

This message was sent by Atlassian JIRA

View raw message