[
https://issues.apache.org/jira/browse/YARN-713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13726750#comment-13726750
]
Omkar Vinit Joshi commented on YARN-713:
----------------------------------------
* Today we are generating ContainerToken and NMToken separately. I guess we
will have to couple both the things together... i.e. if nmtoken creation fails
then there is no point in creating containerTokens for containers present on
that node manager.
* I see one problem in the existing patch which we definitely should address.
In case of DNS hiccups we will keep generating new container Ids without
actually using them.. I don't know if this is a serious issue but will
definitely be annoying for someone trying to monitor application container.
{code}
ContainerId containerId = BuilderUtils.newContainerId(application
.getApplicationAttemptId(), application.getNewContainerId());
{code}
* As AMRMToken also is done irrespective of security need to check if that also
requires similar fixes.
> 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.1.0-beta
>
> 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
