[
https://issues.apache.org/jira/browse/SAMZA-929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16500545#comment-16500545
]
Yi Pan (Data Infrastructure) commented on SAMZA-929:
----------------------------------------------------
[[email protected]] thanks for reporting the test results on this one!
Really appreciated it! What you described sounds right. And yes, the way to
avoid the delay is to set zero to the initial delay. Do you mind to take over
this ticket and submit a PR for this one? Thanks a lot!
-Yi
> Support AM restart in Kerberos secured YARN after the original token in
> launch context expires
> ----------------------------------------------------------------------------------------------
>
> Key: SAMZA-929
> URL: https://issues.apache.org/jira/browse/SAMZA-929
> Project: Samza
> Issue Type: Sub-task
> Components: yarn
> Reporter: Yi Pan (Data Infrastructure)
> Assignee: Chen Song
> Priority: Major
>
> In Kerberos secured YARN cluster, an initial token is given in the launch
> context to RM for a job. When that token expires, RM will not be able to
> restart failed AM. As for now, we will have to re-submit the job to refresh
> the token in the launch context.
> This ticket is searching for a solution that can refresh the token in the
> launch context for AM.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
