You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by GitBox <gi...@apache.org> on 2020/10/23 07:08:39 UTC
[GitHub] [flink] QingdongZeng3 commented on a change in pull request #13690: [FLINK-16595][YARN]support more HDFS nameServices in yarn mode when security enabled. Is…
QingdongZeng3 commented on a change in pull request #13690:
URL: https://github.com/apache/flink/pull/13690#discussion_r510678304
##########
File path: flink-yarn/src/main/java/org/apache/flink/yarn/configuration/YarnConfigOptions.java
##########
@@ -294,6 +294,13 @@
"they doesn't need to be downloaded every time for each application. An example could be " +
"hdfs://$namenode_address/path/of/flink/lib");
+ public static final ConfigOption<List<String>> YARN_ACCESS =
+ key("yarn.access.hadoopFileSystems")
Review comment:
thanks for your suggestion，I will change it.
> I believe it would be good to look into covering this change in our Kerberos end to end tests, to guarantee this is properly working.
>
> You should be able to extend the end to end test defined in `test_yarn_job_kerberos_docker.sh` for this.
> You will probably need to set up a secondary namenode configuration in flink-end-to-end-tests/test-scripts/docker-hadoop-secure-cluster/config, create additional keys in `bootstrap.sh` and launch a second nameNode there.
okay,I will follow your advice.
> I believe it would be good to look into covering this change in our Kerberos end to end tests, to guarantee this is properly working.
>
> You should be able to extend the end to end test defined in `test_yarn_job_kerberos_docker.sh` for this.
> You will probably need to set up a secondary namenode configuration in flink-end-to-end-tests/test-scripts/docker-hadoop-secure-cluster/config, create additional keys in `bootstrap.sh` and launch a second nameNode there.
okay,I will follow your advice. Thanks!
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org