Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/607#discussion_r12175232
--- Diff: docs/configuration.md ---
@@ -679,6 +679,17 @@ Apart from these, the following properties are also
available, and may be useful
Set a special library path to use when launching executor JVM's.
</td>
</tr>
+<tr>
+ <td>spark.user.cacheUserGroupInformation</td>
+ <td>true</td>
+ <td>
+ Caching UGIs is a workaround for
[SPARK-1676](https://issues.apache.org/jira/browse/SPARK-1676)
+ for users who are not using security in a very serious manner. Caching
UGIs can produce
--- End diff --
This sort of implies that we can actually break the hadoop security model
if this is enabled, but I don't think that's true. I just think that some
long-running jobs might have trouble with token renewal.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
