[
https://issues.apache.org/jira/browse/PHOENIX-1395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14216574#comment-14216574
]
Jeffrey Zhong commented on PHOENIX-1395:
----------------------------------------
{quote}
I think there's a patch up already for that
{quote}
The attached patch verifies connection.close() clears up all temp files created
by the connection. [[email protected]] could you check if the attached
test case is already covered otherwise we can get this in to increase test
coverage.
{quote}
Is using File.deleteOnExit() ok?
{quote}
There was an issue Java1.4 on this. So far I doesn't see any issue. It's a nice
to have thing to clear spill files as a last catch-all step.
> 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, PHOENIX-1395.v1.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)
