Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Date: Tue, 21 Mar 2017 00:01:42 +0000 (UTC)
From: "ASF GitHub Bot (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.13049024.1488920889000.73097.1490054502299@Atlassian.JIRA>
In-Reply-To: <JIRA.13049024.1488920889000@Atlassian.JIRA>
References: <JIRA.13049024.1488920889000@Atlassian.JIRA> <JIRA.13049024.1488920889039@jira-lw-us.apache.org>
Subject: [jira] [Commented] (YARN-6302) Fail the node, if Linux Container
 Executor is not configured properly
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Tue, 21 Mar 2017 00:01:46 -0000


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

ASF GitHub Bot commented on YARN-6302:
--------------------------------------

Github user templedf commented on a diff in the pull request:

    https://github.com/apache/hadoop/pull/200#discussion_r107033241
  
    --- Diff: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/main/native/container-executor/impl/container-executor.h ---
    @@ -37,8 +37,8 @@ enum command {
     
     enum errorcodes {
       INVALID_ARGUMENT_NUMBER = 1,
    -  INVALID_USER_NAME, //2
    -  INVALID_COMMAND_PROVIDED, //3
    +  //INVALID_USER_NAME 2
    --- End diff --
    
    This section of code makes me want to weep.


> Fail the node, if Linux Container Executor is not configured properly
> ---------------------------------------------------------------------
>
>                 Key: YARN-6302
>                 URL: https://issues.apache.org/jira/browse/YARN-6302
>             Project: Hadoop YARN
>          Issue Type: Bug
>            Reporter: Miklos Szegedi
>            Assignee: Miklos Szegedi
>            Priority: Minor
>
> We have a cluster that has one node with misconfigured Linux Container Executor. Every time an AM or regular container is launched on the cluster, it will fail. The node will still have resources available, so it keeps failing apps until the administrator notices the issue and decommissions the node. AM Blacklisting only helps, if the application is already running.
> As a possible improvement, when the LCE is used on the cluster and a NM gets certain errors back from the LCE, like error 24 configuration not found, we should not try to allocate anything on the node anymore or shut down the node entirely. That kind of problem normally does not fix itself and it means that nothing can really run on that node.
> {code}
> Application application_1488920587909_0010 failed 2 times due to AM Container for appattempt_1488920587909_0010_000002 exited with exitCode: -1000
> Failing this attempt.Diagnostics: Application application_1488920587909_0010 initialization failed (exitCode=24) with output:
> For more detailed output, check the application tracking page: http://node-1.domain.com:8088/cluster/app/application_1488920587909_0010 Then click on links to logs of each attempt.
> . Failing the application.
> {code}


--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org