You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@samza.apache.org by "Chen Song (JIRA)" <ji...@apache.org> on 2016/04/04 05:11:25 UTC
[jira] [Commented] (SAMZA-727) Support for Kerberos
[ https://issues.apache.org/jira/browse/SAMZA-727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15223626#comment-15223626 ]
Chen Song commented on SAMZA-727:
---------------------------------
If I understand that correctly, I think the launch context that cannot be updated is the launch context for AM but not for containers.
* AM will re-login from the keytab periodically and create new delegation tokens.
* Each time a container is requested or restarted, AM will always use the latest tokens to create the corresponding new launch context for the containers.
> Support for Kerberos
> --------------------
>
> Key: SAMZA-727
> URL: https://issues.apache.org/jira/browse/SAMZA-727
> Project: Samza
> Issue Type: New Feature
> Components: yarn
> Affects Versions: 0.9.0
> Environment: YARN with Kerberos
> Reporter: Qi FU
> Assignee: Chen Song
> Attachments: SAMZA-727.patch
>
>
> Samza doesn't support Kerberos, which is very common for YARN cluster.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)