[
https://issues.apache.org/jira/browse/YARN-713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13759601#comment-13759601
]
Omkar Vinit Joshi commented on YARN-713:
----------------------------------------
Addressing NMToken and ContainerToken issue here. I am now creating
ContainerToken and NMToken together to make sure that we always have both
created.
* first we will create ContainerToken
* then NMToken
if both succeed then only current container will be either assigned or will be
reserved depending on the scheduler logic. However if any of them fails them we
will discard the container and try again later. Added test cases for all 3
schedulers.
> ResourceManager can exit unexpectedly if DNS is unavailable
> -----------------------------------------------------------
>
> Key: YARN-713
> URL: https://issues.apache.org/jira/browse/YARN-713
> Project: Hadoop YARN
> Issue Type: Bug
> Components: resourcemanager
> Affects Versions: 2.1.0-beta
> Reporter: Jason Lowe
> Assignee: Omkar Vinit Joshi
> Priority: Critical
> Fix For: 2.3.0
>
> Attachments: YARN-713.patch, YARN-713.patch, YARN-713.patch,
> YARN-713.patch
>
>
> As discussed in MAPREDUCE-5261, there's a possibility that a DNS outage could
> lead to an unhandled exception in the ResourceManager's AsyncDispatcher, and
> that ultimately would cause the RM to exit. The RM should not exit during
> DNS hiccups.
--
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
