hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Junping Du (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-4527) Possible thread leak if TimelineClient.start() get called multiple times.
Date Wed, 30 Dec 2015 15:33:49 GMT

     [ https://issues.apache.org/jira/browse/YARN-4527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Junping Du updated YARN-4527:
-----------------------------
    Attachment: YARN-4527.patch

Upload a quick patch to fix it. It is quite straightforward so no unit test is needed.

> 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)

Mime
View raw message