[
https://issues.apache.org/jira/browse/SAMZA-727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15181373#comment-15181373
]
Yi Pan (Data Infrastructure) commented on SAMZA-727:
----------------------------------------------------
Hi, [~steve_l], just noticed one thing:
# if the original HDFS delegation token in launch context can not be refreshed,
and AM tries to request a new container to be allocated and launched, the
NodeManager would get the original HDFS delegation token which may have
expired. That will cause the container fails to launch, right? If that is true,
we still have not solved the issue to allow:
## Containers can be launched even after the original HDFS token in the launch
context expires
Is it possible for AM to pass around the new delegation token via NMClient?
> 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
> Fix For: 0.10.1
>
> 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)
