Return-Path: X-Original-To: apmail-hadoop-yarn-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-yarn-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id E83BD18C87 for ; Wed, 30 Dec 2015 15:33:49 +0000 (UTC) Received: (qmail 98077 invoked by uid 500); 30 Dec 2015 15:33:49 -0000 Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org Received: (qmail 98003 invoked by uid 500); 30 Dec 2015 15:33:49 -0000 Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: yarn-issues@hadoop.apache.org Delivered-To: mailing list yarn-issues@hadoop.apache.org Received: (qmail 97913 invoked by uid 99); 30 Dec 2015 15:33:49 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 30 Dec 2015 15:33:49 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 946672C1F55 for ; Wed, 30 Dec 2015 15:33:49 +0000 (UTC) Date: Wed, 30 Dec 2015 15:33:49 +0000 (UTC) From: "Junping Du (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (YARN-4527) Possible thread leak if TimelineClient.start() get called multiple times. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ 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)