hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinod Kumar Vavilapalli (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-3685) NodeManager unnecessarily knows about classpath-jars due to Windows limitations
Date Tue, 19 May 2015 23:47:00 GMT

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

Vinod Kumar Vavilapalli commented on YARN-3685:
-----------------------------------------------

My first reaction is that this jar can be generated by the app (say MR client or AM) and passed
to YARN.

In the worst case, this should get thrown out of ContainerExecutor and instead become a specific
implementation only on the Windows-executor which inspects env variables and does this mangling.

/cc [~cnauroth], [~rusanu] who worked in this area before.

Thoughts?

> 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
>            Reporter: Vinod Kumar Vavilapalli
>            Assignee: 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)

Mime
View raw message