Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Tue, 19 Aug 2014 23:53:19 +0000 (UTC)
From: "Alejandro Abdelnur (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12734607.1408210063124.37837.1408492399056@arcas>
In-Reply-To: <JIRA.12734607.1408210063124@arcas>
References: <JIRA.12734607.1408210063124@arcas>
Subject: [jira] [Commented] (YARN-2424) LCE should support non-cgroups,
 non-secure mode
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Alejandro Abdelnur commented on YARN-2424:
------------------------------------------

You are saying this is proactive troubleshooting then, not meant for production? If so, then, as I said before:

* the property has 'use-only-for-troubleshooting' in its name.
* the NM logs print a WARN at startup and on every started container stating the flag and its un-secure nature
* the container stdout/stderr also print a WARN to alert the user of the cluster setup.

> LCE should support non-cgroups, non-secure mode
> -----------------------------------------------
>
>                 Key: YARN-2424
>                 URL: https://issues.apache.org/jira/browse/YARN-2424
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: nodemanager
>    Affects Versions: 2.3.0, 2.4.0, 2.5.0, 2.4.1
>            Reporter: Allen Wittenauer
>            Priority: Blocker
>         Attachments: YARN-2424.patch
>
>
> After YARN-1253, LCE no longer works for non-secure, non-cgroup scenarios.  This is a fairly serious regression, as turning on LCE prior to turning on full-blown security is a fairly standard procedure.


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