[
https://issues.apache.org/jira/browse/PHOENIX-1395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16029801#comment-16029801
]
Enis Soztutar commented on PHOENIX-1395:
----------------------------------------
bq. on phoenix 4.10 ; seeing around 30G of
"00c53f2c-9c3c-4f61-98ef-30977edbaf825826236490782363992.tmp" and
"ResultSpooler*.bin" files!
Are active queries going on or these are left overs similar to the ones in the
jira description. You can check whether these files are in use (by the region
server or the phoenix client) by doing an lsof.
bq. Is it safe to delete them?
Should be safe if no application has these files for reading or writing.
However, if that is the case, I would suggest to open another jira to track the
bug since this one is pretty old.
> 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)
