[jira] [Commented] (FLINK-8981) End-to-end test: Kerberos security

["Tzu-Li (Gordon) Tai (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/FLINK-8981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16413471#comment-16413471 ] 

Tzu-Li (Gordon) Tai commented on FLINK-8981:
--------------------------------------------

Hi [~suez1224]! Thanks for picking this issue up.

How are you doing with this task? It would be nice to be able to have this set up before the first release candidate for 1.5.0.

I would suggest that for this test, we should try to set up a multi-nodemanager YARN cluster.
Most of the issues we have bumped into with Kerberos on YARN, is that the keytab path is incorrect after a keytab is shipped to different nodemanagers. With a single nodemanager setup, this problem would not surface.

> End-to-end test: Kerberos security
> ----------------------------------
>
>                 Key: FLINK-8981
>                 URL: https://issues.apache.org/jira/browse/FLINK-8981
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Security, Tests
>    Affects Versions: 1.5.0
>            Reporter: Till Rohrmann
>            Assignee: Shuyi Chen
>            Priority: Blocker
>             Fix For: 1.5.0
>
>
> We should add an end-to-end test which verifies Flink's integration with Kerberos security. In order to do this, we should start a Kerberos secured Hadoop, ZooKeeper and Kafka cluster. Then we should start a Flink cluster with HA enabled and run a job which reads from and writes to Kafka. We could use a simple pipe job for that purpose which has some state for checkpointing to HDFS.
> See [security docs| https://ci.apache.org/projects/flink/flink-docs-master/ops/security-kerberos.html] for how more information about Flink's Kerberos integration.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)