[
https://issues.apache.org/jira/browse/YARN-2743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14184349#comment-14184349
]
Jian He commented on YARN-2743:
-------------------------------
bq. why is RMDelegationTokenIdentifier converted to proto? RM is the reader and
writer for this ID, so no need for this to be a proto?
It’ll be useful in rolling upgrades, when RM1 and RM2 have different versions
of the RMDT. i.e. writer of RM1 and reader of RM2 are incompatible.
Fixed other comments.
> Yarn jobs via oozie fail with failed to renew token (secure) or digest
> mismatch (unsecure) errors when RM is being killed
> -------------------------------------------------------------------------------------------------------------------------
>
> Key: YARN-2743
> URL: https://issues.apache.org/jira/browse/YARN-2743
> Project: Hadoop YARN
> Issue Type: Bug
> Components: resourcemanager
> Affects Versions: 2.6.0
> Reporter: Arpit Gupta
> Assignee: Jian He
> Priority: Blocker
> Attachments: YARN-2743.1.patch, YARN-2743.2.patch
>
>
> During our HA testing we have seen yarn jobs run via oozie fail with failed
> to renew delegation token errors on secure clusters and digest mismatch
> errors on un secure clusters
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
