Return-Path: X-Original-To: apmail-spark-issues-archive@minotaur.apache.org Delivered-To: apmail-spark-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 8984E17B18 for ; Thu, 26 Feb 2015 00:51:08 +0000 (UTC) Received: (qmail 87514 invoked by uid 500); 26 Feb 2015 00:51:05 -0000 Delivered-To: apmail-spark-issues-archive@spark.apache.org Received: (qmail 87483 invoked by uid 500); 26 Feb 2015 00:51:05 -0000 Mailing-List: contact issues-help@spark.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@spark.apache.org Received: (qmail 87473 invoked by uid 99); 26 Feb 2015 00:51:05 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 26 Feb 2015 00:51:05 +0000 Date: Thu, 26 Feb 2015 00:51:05 +0000 (UTC) From: "Sean Owen (JIRA)" To: issues@spark.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Resolved] (SPARK-3563) Shuffle data not always be cleaned 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/SPARK-3563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Owen resolved SPARK-3563. ------------------------------ Resolution: Duplicate This is either 'not a problem' (leaking references to RDDs) or is another issue asking 'why does a shuffle file not get deleted?' which I'm hoping to direct to SPARK-5836. It's not quite a duplicate but I believe the underlying issue is the same. > Shuffle data not always be cleaned > ---------------------------------- > > Key: SPARK-3563 > URL: https://issues.apache.org/jira/browse/SPARK-3563 > Project: Spark > Issue Type: Bug > Components: Streaming > Affects Versions: 1.0.2 > Reporter: Hong Shen > > In our cluster, when we run a spark streaming job, after running for many hours, the shuffle data seems not all be cleaned, here is the shuffle data: > -rw-r----- 1 tdwadmin users 23948 Sep 17 13:21 shuffle_132_34_0 > -rw-r----- 1 tdwadmin users 18237 Sep 17 13:32 shuffle_143_22_1 > -rw-r----- 1 tdwadmin users 22934 Sep 17 13:35 shuffle_146_15_0 > -rw-r----- 1 tdwadmin users 27666 Sep 17 13:35 shuffle_146_36_1 > -rw-r----- 1 tdwadmin users 12864 Sep 17 14:05 shuffle_176_12_0 > -rw-r----- 1 tdwadmin users 22115 Sep 17 14:05 shuffle_176_33_1 > -rw-r----- 1 tdwadmin users 15666 Sep 17 14:21 shuffle_192_0_1 > -rw-r----- 1 tdwadmin users 13916 Sep 17 14:38 shuffle_209_53_0 > -rw-r----- 1 tdwadmin users 20031 Sep 17 14:41 shuffle_212_26_0 > -rw-r----- 1 tdwadmin users 15158 Sep 17 14:41 shuffle_212_47_1 > -rw-r----- 1 tdwadmin users 42880 Sep 17 12:12 shuffle_63_1_1 > -rw-r----- 1 tdwadmin users 32030 Sep 17 12:14 shuffle_65_40_0 > -rw-r----- 1 tdwadmin users 34477 Sep 17 12:33 shuffle_84_2_1 > The shuffle data of stage 63, 65, 84, 132... are not cleaned. > In ContextCleaner, it maintains a weak reference for each RDD, ShuffleDependency, and Broadcast of interest, to be processed when the associated object goes out of scope of the application. Actual cleanup is performed in a separate daemon thread. > There must be some reference for ShuffleDependency , and it's hard to find out. -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org For additional commands, e-mail: issues-help@spark.apache.org