phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nick Dimiduk (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PHOENIX-1395) ResultSpooler spill files are left behind in /tmp folder
Date Thu, 06 Nov 2014 21:58:35 GMT

    [ https://issues.apache.org/jira/browse/PHOENIX-1395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14201016#comment-14201016
] 

Nick Dimiduk commented on PHOENIX-1395:
---------------------------------------

Overriding finalize may help, but the results will be unpredictable as the GC makes no guarantees
regarding when it reaps objects.

Better to have the objects expire after some period and have the expiration logic clean up
after them. This would be similar to how HBase RS handles expiring leases on Scanner objects.

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

Mime
View raw message