You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Rohith Sharma K S (JIRA)" <ji...@apache.org> on 2018/08/18 05:42:00 UTC
[jira] [Commented] (YARN-7835) [Atsv2] Race condition in NM while
publishing events if second attempt is launched on the same node
[ https://issues.apache.org/jira/browse/YARN-7835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16584647#comment-16584647 ]
Rohith Sharma K S commented on YARN-7835:
-----------------------------------------
This commit was missing in branch-3.0.. I back ported to branch-3.0..
> [Atsv2] Race condition in NM while publishing events if second attempt is launched on the same node
> ---------------------------------------------------------------------------------------------------
>
> Key: YARN-7835
> URL: https://issues.apache.org/jira/browse/YARN-7835
> Project: Hadoop YARN
> Issue Type: Bug
> Reporter: Rohith Sharma K S
> Assignee: Rohith Sharma K S
> Priority: Critical
> Fix For: 3.1.0, 2.10.0
>
> Attachments: YARN-7835.001.patch, YARN-7835.002.patch, YARN-7835.003.patch, YARN-7835.004.patch
>
>
> It is observed race condition that if master container is killed for some reason and launched on same node then NMTimelinePublisher doesn't add timelineClient. But once completed container for 1st attempt has come then NMTimelinePublisher removes the timelineClient.
> It causes all subsequent event publishing from different client fails to publish with exception Application is not found. !
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org