Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Wed, 27 May 2015 04:36:18 +0000 (UTC)
From: "Chris Nauroth (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12831217.1432078901000.35186.1432701378117@Atlassian.JIRA>
In-Reply-To: <JIRA.12831217.1432078901000@Atlassian.JIRA>
References: <JIRA.12831217.1432078901000@Atlassian.JIRA>
 <JIRA.12831217.1432078901512@arcas>
Subject: [jira] [Commented] (YARN-3685) NodeManager unnecessarily knows
 about classpath-jars due to Windows limitations
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Chris Nauroth commented on YARN-3685:
-------------------------------------

bq. YARN_APPLICATION_CLASSPATH is essentially unused.

In that case, this is definitely worth revisiting as part of this issue.  Perhaps it's not a problem anymore.  This had been used in the past, as seen in bug reports like YARN-1138.

> NodeManager unnecessarily knows about classpath-jars due to Windows limitations
> -------------------------------------------------------------------------------
>
>                 Key: YARN-3685
>                 URL: https://issues.apache.org/jira/browse/YARN-3685
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: nodemanager
>            Reporter: Vinod Kumar Vavilapalli
>
> Found this while looking at cleaning up ContainerExecutor via YARN-3648, making it a sub-task.
> YARN *should not* know about classpaths. Our original design modeled around this. But when we added windows suppport, due to classpath issues, we ended up breaking this abstraction via YARN-316. We should clean this up.


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