[
https://issues.apache.org/jira/browse/TEZ-949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13943720#comment-13943720
]
Bikas Saha commented on TEZ-949:
--------------------------------
If we are using appId then it is necessary to move this logic into the client?
Avoid moving JobTokenSecretManager etc. into tez-api? This calculation of token
should be identical and idempotent in every AM retry, right?
> Handle Session Tokens for Recovery
> ----------------------------------
>
> Key: TEZ-949
> URL: https://issues.apache.org/jira/browse/TEZ-949
> Project: Apache Tez
> Issue Type: Sub-task
> Reporter: Siddharth Seth
> Assignee: Hitesh Shah
> Fix For: 0.4.0
>
> Attachments: TEZ-949.1.patch, TEZ-949.2.patch
>
>
> The tokens used by Fetchers to connect to the ShuffleHandler are generated in
> the AM. Once an AM is restarted, the token will be regenerated - and new
> Reduces will not be able to fetch output from previous Mappers.
> Similar to MAPREDUCE-5042.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
