[
https://issues.apache.org/jira/browse/YARN-690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13662105#comment-13662105
]
Robert Joseph Evans commented on YARN-690:
------------------------------------------
Vinod,
Yes creating and resolving a JIRA in 2 hours is not ideal, but this is a
Blocker that consisted on only a handful of lines of change, also the bylaws
explicitly state that a waiting period is not needed for this vote because
committers can retroactively -1 and pull the change out. I agree that waiting
to let others look at the code is good and if it were not a Blocker I would
have waited.
> RM exits on token cancel/renew problems
> ---------------------------------------
>
> Key: YARN-690
> URL: https://issues.apache.org/jira/browse/YARN-690
> Project: Hadoop YARN
> Issue Type: Bug
> Components: resourcemanager
> Affects Versions: 3.0.0, 0.23.7, 2.0.5-beta
> Reporter: Daryn Sharp
> Assignee: Daryn Sharp
> Priority: Blocker
> Fix For: 3.0.0, 2.0.5-beta, 0.23.8
>
> Attachments: YARN-690.patch, YARN-690.patch
>
>
> The DelegationTokenRenewer thread is critical to the RM. When a
> non-IOException occurs, the thread calls System.exit to prevent the RM from
> running w/o the thread. It should be exiting only on non-RuntimeExceptions.
> The problem is especially bad in 23 because the yarn protobuf layer converts
> IOExceptions into UndeclaredThrowableExceptions (RuntimeException) which
> causes the renewer to abort the process. An UnknownHostException takes down
> the RM...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
