[
https://issues.apache.org/jira/browse/YARN-1025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13729549#comment-13729549
]
Kihwal Lee commented on YARN-1025:
----------------------------------
On Linux, use of LD_LIBRARY_PATH is better because it's easier to manipulate
(e.g. path munging) and offers a better search and error handling. When
java.library.path is set, jvm tries to load the first match. If it fails, the
failure is permanent. I.e. no further search is done. This is unacceptable if
the search paths contain libraries for multiple architectures (e.g. 32 bit and
64 bit). When LD_LIBRARY_PATH is used exclusively, the system loader is in
charge and it does a much better job. I believe the behavior is similar on
Windows with PATH.
> NodeManager does not propagate java.library.path to launched child containers
> on Windows
> ----------------------------------------------------------------------------------------
>
> Key: YARN-1025
> URL: https://issues.apache.org/jira/browse/YARN-1025
> Project: Hadoop YARN
> Issue Type: Bug
> Components: nodemanager
> Affects Versions: 3.0.0, 2.1.1-beta
> Reporter: Chris Nauroth
>
> Neither the NodeManager process itself nor the child container processes that
> it launches have the correct setting for java.library.path on Windows. This
> prevents the processes from loading native code from hadoop.dll. The native
> code is required for correct functioning on Windows (not optional), so this
> ultimately can cause failures in MapReduce jobs.
--
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
