Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/10699#discussion_r49327991
--- Diff: docs/running-on-yarn.md ---
@@ -260,10 +260,10 @@ If you need a reference to the proper location to put
log files in the YARN so t
<td>(none)</td>
<td>
A comma-separated list of secure HDFS namenodes your Spark application
is going to access. For
- example,
<code>spark.yarn.access.namenodes=hdfs://nn1.com:8032,hdfs://nn2.com:8032</code>.
- The Spark application must have access 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
+ example,
<code>spark.yarn.access.namenodes=hdfs://nn1.com:8032,hdfs://nn2.com:8032,
+ webhdfs://nn3.com:50070</code>. The Spark application must have access
to the namenodes listed
--- End diff --
Is it normal to mix different schemes like this? or would it be better to
break this out into a separate sentence/example? just calling attention to
`webhdfs` seems fine.
---
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.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
