[
https://issues.apache.org/jira/browse/YARN-5373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15431754#comment-15431754
]
Daniel Templeton commented on YARN-5373:
----------------------------------------
NIO.2 has some spotty support for setting facls, but it's not supported on
ext4, and maybe not ext3 either. In order to implement an facl, we'll have to
punch out to native code. The code would land in the {{RawLocalFileSystem}} in
common via JNI. I can see where setting the facl is a cleaner solution at a
high level, but JNI is icky by definition. In the LCE we already have a
mechanism defined to punch out to native code without the risk of JNI, so I
can't say that the facl solution is clearly better. Thoughts, [~sjlee0]?
> NPE listing wildcard directory in containerLaunch
> -------------------------------------------------
>
> Key: YARN-5373
> URL: https://issues.apache.org/jira/browse/YARN-5373
> Project: Hadoop YARN
> Issue Type: Bug
> Components: nodemanager
> Affects Versions: 2.9.0
> Reporter: Haibo Chen
> Assignee: Daniel Templeton
> Priority: Blocker
> Attachments: YARN-5373.001.patch, YARN-5373.002.patch,
> YARN-5373.003.patch
>
>
> YARN-4958 added support for wildcards in file localization. It introduces a
> NPE
> at
> {code:java}
> for (File wildLink : directory.listFiles()) {
> sb.symlink(new Path(wildLink.toString()), new Path(wildLink.getName()));
> }
> {code}
> When directory.listFiles returns null (only happens in a secure cluster), NPE
> will cause the container fail to launch.
> Hive, Oozie jobs fail as a result.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
