[
https://issues.apache.org/jira/browse/SPARK-21521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16099100#comment-16099100
]
Marcelo Vanzin commented on SPARK-21521:
----------------------------------------
Hmm, if you're using a local FS it should work since root there should be able
to read everything.
[~jerryshao] do you think the {{checkAccessPermission}} code you added could be
misbehaving here? It doesn't seem to treat any user as special, so maybe.
[~abridgett] you could try setting the directory's permissions to {{4755}};
that should mimic the HDFS behavior of inheriting the directory's group when
creating new files.
> History service requires user is in any group
> ---------------------------------------------
>
> Key: SPARK-21521
> URL: https://issues.apache.org/jira/browse/SPARK-21521
> Project: Spark
> Issue Type: Bug
> Components: Spark Core
> Affects Versions: 2.2.0
> Reporter: Adrian Bridgett
>
> (Regression cf. 2.0.2)
> We run spark as several users, these write to the history location where the
> files are saved as those users with permissions of 770 (this is hardcoded in
> EventLoggingListener.scala).
> The history service runs as root so that it has permissions on these files
> (see https://spark.apache.org/docs/latest/security.html).
> This worked fine in v2.0.2, however in v2.2.0 the events are being skipped
> unless I add the root user into each users group at which point they are seen.
> We currently have all acls configuration unset.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
