[
https://issues.apache.org/jira/browse/YARN-316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13561891#comment-13561891
]
Bikas Saha commented on YARN-316:
---------------------------------
I am in favor of keeping a windows specific path for classpath jar now and
definitely open a jira to merge the code paths later on. I would be wary of
destabilizing the linux path while edge cases and other bugs gets ironed out on
windows. The perf needs to be measured. The branch-1-win jira should have some
discussion on perf tests conducted to measure the difference. We might need to
redo them for trunk because the code is different and perf results might be
different.
Please ignore strsubstitutor. Doesnt seem worth the effort.
So even the simple class name and symlink are just about working for the
current set of test case names. We might need another fix for this down the
road.
> YARN container launch may exceed maximum Windows command line length due to
> long classpath
> ------------------------------------------------------------------------------------------
>
> Key: YARN-316
> URL: https://issues.apache.org/jira/browse/YARN-316
> Project: Hadoop YARN
> Issue Type: Bug
> Components: nodemanager
> Affects Versions: 3.0.0, trunk-win
> Reporter: Chris Nauroth
> Assignee: Chris Nauroth
> Attachments: YARN-316-branch-trunk-win.1.patch,
> YARN-316-branch-trunk-win.2.patch
>
>
> On Windows, a command line longer than 8192 characters will fail. This can
> cause YARN container launch to fail on Windows if the classpath argument
> exceeds this limit.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
