[
https://issues.apache.org/jira/browse/YARN-2836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brahma Reddy Battula updated YARN-2836:
---------------------------------------
Target Version/s: 3.4.0 (was: 3.3.0)
Bulk update: moved all 3.3.0 non-blocker issues, please move back if it is a
blocker.
> RM behaviour on token renewal failures is broken
> ------------------------------------------------
>
> Key: YARN-2836
> URL: https://issues.apache.org/jira/browse/YARN-2836
> Project: Hadoop YARN
> Issue Type: Bug
> Components: resourcemanager
> Reporter: Vinod Kumar Vavilapalli
> Assignee: Vinod Kumar Vavilapalli
> Priority: Major
>
> Found this while reviewing YARN-2834.
> We now completely ignore token renewal failures. For things like Timeline
> tokens which are automatically obtained whether the app needs it or not (we
> should fix this to be user driven), we can ignore failures. But for HDFS
> Tokens etc, ignoring failures is bad because it (1) wastes resources as AMs
> will continue and eventually fail (2) app doesn't know what happened it fails
> eventually.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
