You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@asterixdb.apache.org by "Chen Li (JIRA)" <ji...@apache.org> on 2016/12/19 04:50:59 UTC

[jira] [Commented] (ASTERIXDB-1751) Some of spilled partition files are not deleted properly after the optimized hybrid hash join finishes.

    [ 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)