flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Niels Basjes (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-3670) Kerberos: Improving long-running streaming jobs
Date Fri, 08 Apr 2016 11:41:25 GMT

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

Niels Basjes commented on FLINK-3670:
-------------------------------------

A while ago I found that part of the problem is in the upstream tools that are used. 
See a similar bug report for Spark (SPARK-11182) and what looks like an important blocker
to really fix this HDFS-9276 

> Kerberos: Improving long-running streaming jobs
> -----------------------------------------------
>
>                 Key: FLINK-3670
>                 URL: https://issues.apache.org/jira/browse/FLINK-3670
>             Project: Flink
>          Issue Type: Improvement
>          Components: Command-line client, Local Runtime
>            Reporter: Maximilian Michels
>
> We have seen in the past, that Hadoop's delegation tokens are subject to a number of
subtle token renewal bugs. In addition, they have a maximum life time that can be worked around
but is very inconvenient for the user.
> As per [mailing list discussion|http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/Kerberos-for-Streaming-amp-Kafka-td10906.html],
a way to work around the maximum life time of DelegationTokens would be to pass the Kerberos
principal and key tab upon job submission. A daemon could then periodically renew the ticket.




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message