You are viewing a plain text version of this content. The canonical link for it is here.
Posted to reviews@spark.apache.org by tgravescs <gi...@git.apache.org> on 2016/01/11 15:25:56 UTC
[GitHub] spark pull request: [SPARK-2930] clarify docs on using webhdfs wit...
GitHub user tgravescs opened a pull request:
https://github.com/apache/spark/pull/10699
[SPARK-2930] clarify docs on using webhdfs with spark.yarn.access.nam…
…enodes
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/tgravescs/spark SPARK-2930
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/spark/pull/10699.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #10699
----
commit f304363ce4e46f72ec745fbd9b02a5912a86783e
Author: Tom Graves <tg...@yahoo-inc.com>
Date: 2016-01-11T14:24:47Z
[SPARK-2930] clarify docs on using webhdfs with spark.yarn.access.namenodes
----
---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscribe@spark.apache.org
For additional commands, e-mail: reviews-help@spark.apache.org
[GitHub] spark pull request: [SPARK-2930] clarify docs on using webhdfs wit...
Posted by AmplabJenkins <gi...@git.apache.org>.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10699#issuecomment-170574209
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/49148/
Test PASSed.
---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscribe@spark.apache.org
For additional commands, e-mail: reviews-help@spark.apache.org
[GitHub] spark pull request: [SPARK-2930] clarify docs on using webhdfs wit...
Posted by SparkQA <gi...@git.apache.org>.
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10699#issuecomment-170567981
**[Test build #49148 has started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49148/consoleFull)** for PR 10699 at commit [`f304363`](https://github.com/apache/spark/commit/f304363ce4e46f72ec745fbd9b02a5912a86783e).
---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscribe@spark.apache.org
For additional commands, e-mail: reviews-help@spark.apache.org
[GitHub] spark pull request: [SPARK-2930] clarify docs on using webhdfs wit...
Posted by tgravescs <gi...@git.apache.org>.
Github user tgravescs commented on a diff in the pull request:
https://github.com/apache/spark/pull/10699#discussion_r49344162
--- 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 --
Its fine to mix schemas it really just depends on what your access pattern is and where the cluster is located (regionally). Generally we recommend webhdfs for reading only and only use it when needed (cross colo or incompatibility in versions). If your spark application is reading or writing from 2 different clusters its fine to mix, one might be in the same colo and another cross colo.
I was just hoping to point out that it can be used with webhdfs also and leave it up to the user to know what webhdfs is and when its used based on their deployments. If you think it would be clearer to break out to a sentence I'm fine with that
---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscribe@spark.apache.org
For additional commands, e-mail: reviews-help@spark.apache.org
[GitHub] spark pull request: [SPARK-2930] clarify docs on using webhdfs wit...
Posted by srowen <gi...@git.apache.org>.
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/10699#issuecomment-171955921
Merged to master
---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscribe@spark.apache.org
For additional commands, e-mail: reviews-help@spark.apache.org
[GitHub] spark pull request: [SPARK-2930] clarify docs on using webhdfs wit...
Posted by SparkQA <gi...@git.apache.org>.
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10699#issuecomment-170574029
**[Test build #49148 has finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49148/consoleFull)** for PR 10699 at commit [`f304363`](https://github.com/apache/spark/commit/f304363ce4e46f72ec745fbd9b02a5912a86783e).
* This patch passes all tests.
* This patch merges cleanly.
* This patch adds no public classes.
---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscribe@spark.apache.org
For additional commands, e-mail: reviews-help@spark.apache.org
[GitHub] spark pull request: [SPARK-2930] clarify docs on using webhdfs wit...
Posted by asfgit <gi...@git.apache.org>.
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/10699
---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscribe@spark.apache.org
For additional commands, e-mail: reviews-help@spark.apache.org
[GitHub] spark pull request: [SPARK-2930] clarify docs on using webhdfs wit...
Posted by srowen <gi...@git.apache.org>.
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscribe@spark.apache.org
For additional commands, e-mail: reviews-help@spark.apache.org
[GitHub] spark pull request: [SPARK-2930] clarify docs on using webhdfs wit...
Posted by AmplabJenkins <gi...@git.apache.org>.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10699#issuecomment-170574208
Merged build finished. Test PASSed.
---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscribe@spark.apache.org
For additional commands, e-mail: reviews-help@spark.apache.org