[
https://issues.apache.org/jira/browse/PHOENIX-1395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14200614#comment-14200614
]
Alicia Ying Shu edited comment on PHOENIX-1395 at 11/8/14 11:10 PM:
--------------------------------------------------------------------
If ResultSets, statements and connections are closed properly, the tmp files
should be deleted as part of the close() method. Add a patch to delete tmp
files when JVM exits.
was (Author: aliciashu):
If ResultSets, statements and connections are closed properly, the tmp files
should be deleted as part of the close() method. Add a patch to delete tmp
files when JVM exits. However if the result iterators were still active when
statement or connection close() was called, the close() may be a no-op.
> ResultSpooler spill files are left behind in /tmp folder
> --------------------------------------------------------
>
> Key: PHOENIX-1395
> URL: https://issues.apache.org/jira/browse/PHOENIX-1395
> Project: Phoenix
> Issue Type: Bug
> Reporter: Jeffrey Zhong
> Assignee: Alicia Ying Shu
> Fix For: 4.2
>
> Attachments: PHOENIX-1395.patch
>
>
> Recently we found that some ResultSpooler*.bin files left in the tmp folder.
> I think those are due to some client code doesn't call close on the returned
> Resultset(which internally will invoke underlying
> OnDiskResultIterator.close()) or client code get killed during result
> iterating.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
