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 560FF18C35 for ; Tue, 6 Oct 2015 02:49:27 +0000 (UTC) Received: (qmail 2650 invoked by uid 500); 6 Oct 2015 02:49:27 -0000 Delivered-To: apmail-spark-issues-archive@spark.apache.org Received: (qmail 2487 invoked by uid 500); 6 Oct 2015 02:49:27 -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 2476 invoked by uid 99); 6 Oct 2015 02:49:27 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 06 Oct 2015 02:49:27 +0000 Date: Tue, 6 Oct 2015 02:49:26 +0000 (UTC) From: "Nick Pritchard (JIRA)" To: issues@spark.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (SPARK-10942) Not all cached RDDs are unpersisted MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Nick Pritchard created SPARK-10942: -------------------------------------- Summary: Not all cached RDDs are unpersisted Key: SPARK-10942 URL: https://issues.apache.org/jira/browse/SPARK-10942 Project: Spark Issue Type: Bug Components: Streaming Reporter: Nick Pritchard I have a Spark Streaming application that caches RDDs inside of a {{transform}} closure. Looking at the Spark UI, it seems that most of these RDDs are unpersisted after the batch completes, but not all. I have copied a minimal reproducible example below to highlight the problem. I run this and monitor the Spark UI "Storage" tab. The example generates and caches 30 RDDs, and I see most get cleaned up. However in the end, some still remain cached. There is some randomness going on because I see different RDDs remain cached for each run. I have marked this as Major because I haven't been able to workaround it and it is a memory leak for my application. I tried setting {{spark.cleaner.ttl}} but that did not change anything. {code} val inputRDDs = mutable.Queue.tabulate(30) { i => sc.parallelize(Seq(i)) } val input: DStream[Int] = ssc.queueStream(inputRDDs) val output = input.transform { rdd => if (rdd.isEmpty()) { rdd } else { val rdd2 = rdd.map(identity) rdd2.setName(rdd.first().toString) rdd2.cache() val rdd3 = rdd2.map(identity) rdd3 } } output.print() ssc.start() ssc.awaitTermination() {code} -- 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