Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 27437200BF2 for ; Mon, 19 Dec 2016 05:51:05 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 25E4A160B36; Mon, 19 Dec 2016 04:51:05 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 70FA2160B30 for ; Mon, 19 Dec 2016 05:51:04 +0100 (CET) Received: (qmail 1459 invoked by uid 500); 19 Dec 2016 04:51:03 -0000 Mailing-List: contact notifications-help@asterixdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@asterixdb.apache.org Delivered-To: mailing list notifications@asterixdb.apache.org Received: (qmail 1450 invoked by uid 99); 19 Dec 2016 04:51: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; Mon, 19 Dec 2016 04:51: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 3D1B91A0280 for ; Mon, 19 Dec 2016 04:51:03 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -6.219 X-Spam-Level: X-Spam-Status: No, score=-6.219 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, KAM_LAZY_DOMAIN_SECURITY=1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-2.999] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id OnGs0I7Jj6t8 for ; Mon, 19 Dec 2016 04:51:01 +0000 (UTC) Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with SMTP id 68F8F5F2EF for ; Mon, 19 Dec 2016 04:51:00 +0000 (UTC) Received: (qmail 1422 invoked by uid 99); 19 Dec 2016 04:50:59 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 19 Dec 2016 04:50:59 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 86E532C0057 for ; Mon, 19 Dec 2016 04:50:59 +0000 (UTC) Date: Mon, 19 Dec 2016 04:50:59 +0000 (UTC) From: "Chen Li (JIRA)" To: notifications@asterixdb.incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (ASTERIXDB-1751) Some of spilled partition files are not deleted properly after the optimized hybrid hash join finishes. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Mon, 19 Dec 2016 04:51:05 -0000 [ https://issues.apache.org/jira/browse/ASTERIXDB-1751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15760144#comment-15760144 ] Chen Li commented on ASTERIXDB-1751: ------------------------------------ Does it mean the main reason is that a partition file is not closed properly? The fix is to call close() properly? > Some of spilled partition files are not deleted properly after the optimized hybrid hash join finishes. > ------------------------------------------------------------------------------------------------------- > > Key: ASTERIXDB-1751 > URL: https://issues.apache.org/jira/browse/ASTERIXDB-1751 > Project: Apache AsterixDB > Issue Type: Bug > Reporter: Taewoo Kim > Assignee: Taewoo Kim > > Some of spilled partition files are not deleted. The condition is: > 1) A partition is spilled to the disk during the build phase. > 2) That partition doesn't receive any tuple after that spill. > Then, the file is not explicitly closed during "closeAllSpilledPartition" call. So, during the probe phase, even though the file will be open again with "delete on close call". When closing the file, since a file handle is still holding the file, it is not deleted properly. -- This message was sent by Atlassian JIRA (v6.3.4#6332)