From issues-return-198671-archive-asf-public=cust-asf.ponee.io@spark.apache.org Sat Aug 11 21:14:04 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id 65E53180662 for ; Sat, 11 Aug 2018 21:14:04 +0200 (CEST) Received: (qmail 65138 invoked by uid 500); 11 Aug 2018 19:14:03 -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 65129 invoked by uid 99); 11 Aug 2018 19:14:03 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 11 Aug 2018 19:14:03 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 021761A0488 for ; Sat, 11 Aug 2018 19:14:03 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -109.501 X-Spam-Level: X-Spam-Status: No, score=-109.501 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, KAM_ASCII_DIVIDERS=0.8, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id VOpa__xqYxmF for ; Sat, 11 Aug 2018 19:14:02 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id BCD7E5F174 for ; Sat, 11 Aug 2018 19:14:01 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 4E065E0047 for ; Sat, 11 Aug 2018 19:14:01 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 0679123F99 for ; Sat, 11 Aug 2018 19:14:00 +0000 (UTC) Date: Sat, 11 Aug 2018 19:14:00 +0000 (UTC) From: "Yunling Cai (JIRA)" To: issues@spark.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (SPARK-25091) Spark Thrift Server: UNCACHE TABLE and CLEAR CACHE does not clean up executor memory MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/SPARK-25091?page=3Dcom.atlassi= an.jira.plugin.system.issuetabpanels:all-tabpanel ] Yunling Cai updated SPARK-25091: -------------------------------- Description:=20 UNCACHE TABLE and CLEAR CACHE does not clean up executor memory. Through Spark UI, although in Storage, we see the cached table removed. In = Executor, the executors continue to hold the RDD and the memory is not clea= red. This results in huge=C2=A0waste in executor memory usage. As we call C= ACHE TABLE, we run into issues where the cached tables are spilled to disk = instead of reclaiming the memory storage.=C2=A0 Steps to reproduce: CACHE TABLE=C2=A0test.test_cache; UNCACHE TABLE test.test_cache; =3D=3D Storage shows table is not cached; Executor shows the executor stora= ge memory does not change =3D=3D=C2=A0 CACHE TABLE test.test_cache; CLEAR CACHE; =3D=3D Storage shows table is not cached; Executor shows the executor stora= ge memory does not change =3D=3D=C2=A0 was: UNCACHE TABLE and CLEAR CACHE does not clean up executor memory. Through Spark UI, although in Storage, we see the cached table removed. In = Executor, the executors continue to hold the RDD and the memory is not clea= red. This results in huge=C2=A0waste in executor memory usage. As we call C= ACHE TABLE, we run into issues where the cached tables are spilled to disk = instead of reclaiming the memory storage.=C2=A0 > Spark Thrift Server: UNCACHE TABLE and CLEAR CACHE does not clean up exec= utor memory > -------------------------------------------------------------------------= ----------- > > Key: SPARK-25091 > URL: https://issues.apache.org/jira/browse/SPARK-25091 > Project: Spark > Issue Type: Bug > Components: Spark Core > Affects Versions: 2.3.1 > Reporter: Yunling Cai > Priority: Major > > UNCACHE TABLE and CLEAR CACHE does not clean up executor memory. > Through Spark UI, although in Storage, we see the cached table removed. I= n Executor, the executors continue to hold the RDD and the memory is not cl= eared. This results in huge=C2=A0waste in executor memory usage. As we call= CACHE TABLE, we run into issues where the cached tables are spilled to dis= k instead of reclaiming the memory storage.=C2=A0 > Steps to reproduce: > CACHE TABLE=C2=A0test.test_cache; > UNCACHE TABLE test.test_cache; > =3D=3D Storage shows table is not cached; Executor shows the executor sto= rage memory does not change =3D=3D=C2=A0 > CACHE TABLE test.test_cache; > CLEAR CACHE; > =3D=3D Storage shows table is not cached; Executor shows the executor sto= rage memory does not change =3D=3D=C2=A0 -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org For additional commands, e-mail: issues-help@spark.apache.org