phoenix-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From <marks1900-pos...@yahoo.com.au>
Subject Re: Getting swamped with Phoenix *.tmp files on SELECT.
Date Mon, 18 Apr 2016 15:54:45 GMT
Currently I am running out of disk space as a direct result of these spool temp files (350GB
+), any ideas on how to address this?  These .tmp files never seem to be cleaned up after
each query.  Is there any work-around?

      From: Samarth Jain <samarth.jain@gmail.com>
 To: "user@phoenix.apache.org" <user@phoenix.apache.org> 
Sent: Friday, 15 April 2016, 17:00
 Subject: Re: Getting swamped with Phoenix *.tmp files on SELECT.
   
FWIW, with phoenix 4.7, we no longer need to spool results on the client. Instead we rely
on pacing scanners as and when needed. To utitlize the feature though, you would need to make
sure that you are using HBase versions that are at least as new as:
HBase 0.98.17 for HBase 0.98HBase 1.0.3 for HBase 1.0HBase 1.1.3 for HBase 1.1 and beyond 

On Fri, Apr 15, 2016 at 1:51 PM, Alok Singh <alok@cloudability.com> wrote:

We ran into something similar, here is the ticket https://issues.apache.org/jira/browse/PHOENIX-2685The
work around that mitigated this issue for us was to lower the value of phoenix.query.spoolThresholdBytes
to 10 MB. It is counter intuitive, but, due to the way the spooling iterator interacts with
global memory manager, it works.
Alok

Alok
alok@cloudability.com
On Fri, Apr 15, 2016 at 1:42 PM, <Mark> wrote:

I am using an Ambari HDP distribution of the Phoenix client (/usr/hdp/2.3.4.0-3485/phoenix/phoenix-4.4.0.2.3.4.0-3485-client.jar),
and to close database connections I am using the standard Java JDBC try-with-resources process
 (http://www.mastertheboss.com/jboss-server/jboss-datasource/using-try-with-resources-to-close-database-connections
, https://docs.oracle.com/javase/tutorial/essential/exceptions/tryResourceClose.html).

      From: Samarth Jain
Sent: Friday, 15 April 2016, 16:03
 Subject: Re: Getting swamped with Phoenix *.tmp files on SELECT.
  
What version of phoenix are you using? Is the application properly closing statements and
result sets?

On Friday, April 15, 2016, wrote:

I am running into an issue where a huge number temporary files are being created in my C:\Users\myuser\AppData\Local\Temp
folder, they are around 20MB big and never get cleaned up.  These *.tmp files grew to around
200GB before I stopped the server.
Example file names:
7a0967de-9dff-432b-bcfe-de30bc630add5176202498513378657.tmp
813e40e1-afa9-4847-919c-7c55f95f8a475501154042645376476.tmp
1329da43-561d-4e68-9120-56bd650a6ac98781585316402092121.tmp

Currently, I have my Phoenix Client jar deployed to Wildfly 10 as described here:  https://docs.jboss.org/author/display/TEIID/Phoenix+Data+Sources
These *.tmp files only appear when I run SELECT queries.
Any help would be appreciated.


   





  
Mime
View raw message