Github user vanzin commented on a diff in the pull request:
https://github.com/apache/spark/pull/1159#discussion_r14142240
--- Diff: docs/running-on-yarn.md ---
@@ -106,6 +106,13 @@ Most of the configs are the same for Spark on YARN as
for other deployment modes
set this configuration to "hdfs:///some/path".
</td>
</tr>
+<tr>
+ <td><code>spark.yarn.access.namenodes</code></td>
+ <td>(none)</td>
+ <td>
+ A list of secure HDFS namenodes your Spark application is going to
access. For example,
`spark.yarn.access.namenodes=hdfs://nn1.com:8032,hdfs://nn2.com:8032`. The
Spark application must have acess to the namenodes listed and Kerberos must be
properly configured to be able to access them (either in the same realm or in a
trusted realm). Spark acquires security tokens for each of the namenodes so
that the Spark application can access those remote HDFS clusters.
--- End diff --
LGTM.
BTW, I know it's the current style of the file, but these long lines could
use some breaks.
---
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.
---
