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 "Steve Loughran (JIRA)" <ji...@apache.org> on 2016/01/01 18:38:39 UTC

[jira] [Commented] (YARN-4527) Possible thread leak if TimelineClient.start() get called multiple times.

    [ https://issues.apache.org/jira/browse/YARN-4527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15076345#comment-15076345 ] 

Steve Loughran commented on YARN-4527:
--------------------------------------

the yarn service state machine guarantees that serviceStart() will not be  called more than once

> Possible thread leak if TimelineClient.start() get called multiple times.
> -------------------------------------------------------------------------
>
>                 Key: YARN-4527
>                 URL: https://issues.apache.org/jira/browse/YARN-4527
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: timelineserver
>    Affects Versions: 2.8.0
>            Reporter: Junping Du
>            Assignee: Junping Du
>         Attachments: YARN-4527.patch
>
>
> Since YARN-4234, we involve TimelineClient start and stop that would create different TimelineWriter according to the configuration. serviceStart() will create a TimelineWriter instance every time which will spawn several timer threads afterwards. If one TimelineClient get call start() multiple times for some reason (application bug or intentionally in some cases), the spawned timer threads will get leak.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)