You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2018/02/02 14:49:00 UTC

[jira] [Commented] (FLINK-8275) Flink YARN deployment with Kerberos enabled not working

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

ASF GitHub Bot commented on FLINK-8275:
---------------------------------------

Github user tzulitai commented on a diff in the pull request:

    https://github.com/apache/flink/pull/5172#discussion_r165635517
  
    --- Diff: flink-yarn/src/main/java/org/apache/flink/yarn/YarnApplicationMasterRunner.java ---
    @@ -170,9 +160,10 @@ protected int run(String[] args) {
     
     			final Configuration flinkConfig = createConfiguration(currDir, dynamicProperties);
     
    -			// set keytab principal and replace path with the local path of the shipped keytab file in NodeManager
    -			if (keytabPath != null && remoteKeytabPrincipal != null) {
    -				flinkConfig.setString(SecurityOptions.KERBEROS_LOGIN_KEYTAB, keytabPath);
    +			File f = new File(currDir, Utils.KEYTAB_FILE_NAME);
    +			if (remoteKeytabPrincipal != null && f.exists()) {
    --- End diff --
    
    Can we re-add the debug log `LOG.debug("keytabPath: {}", keytabPath);` to provide more visibility to this?


> Flink YARN deployment with Kerberos enabled not working 
> --------------------------------------------------------
>
>                 Key: FLINK-8275
>                 URL: https://issues.apache.org/jira/browse/FLINK-8275
>             Project: Flink
>          Issue Type: Bug
>          Components: Security
>    Affects Versions: 1.4.0
>            Reporter: Shuyi Chen
>            Assignee: Shuyi Chen
>            Priority: Blocker
>             Fix For: 1.5.0, 1.4.1
>
>
> The local keytab path in YarnTaskManagerRunner is incorrectly set to the ApplicationMaster's local keytab path. This causes jobs to fail because the TaskManager can't read the keytab.



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