You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "sanket patel (JIRA)" <ji...@apache.org> on 2017/05/30 11:23:04 UTC
[jira] [Commented] (PHOENIX-1395) ResultSpooler spill files are
left behind in /tmp folder
[ https://issues.apache.org/jira/browse/PHOENIX-1395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16029278#comment-16029278 ]
sanket patel commented on PHOENIX-1395:
---------------------------------------
on phoenix 4.10 ; seeing around 30G of "00c53f2c-9c3c-4f61-98ef-30977edbaf825826236490782363992.tmp" and "ResultSpooler*.bin" files!
Is it safe to delete them?
> 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.3.0, 3.3.0
>
> 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.15#6346)