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

ASF GitHub Bot commented on DRILL-2100:
---------------------------------------

Github user jaltekruse commented on a diff in the pull request:

    https://github.com/apache/drill/pull/454#discussion_r57955905
  
    --- Diff: 
exec/java-exec/src/main/java/org/apache/drill/exec/physical/impl/xsort/ExternalSortBatch.java
 ---
    @@ -110,11 +111,12 @@
       private LinkedList<BatchGroup> batchGroups = Lists.newLinkedList();
       private LinkedList<BatchGroup> spilledBatchGroups = 
Lists.newLinkedList();
       private SelectionVector4 sv4;
    -  private FileSystem fs;
    +  private static FileSystem fs;
    --- End diff --
    
    Won't making this static and closing it cause other queries with an 
external sort to fail? You should be able to put this in the close() method of 
this class so that it only impacts the local instance. It looks like the 
directory created includes the operator ID, so there shouldn't be a need to 
keep around the spill directory until the foreman close method.


> Drill not deleting spooling files
> ---------------------------------
>
>                 Key: DRILL-2100
>                 URL: https://issues.apache.org/jira/browse/DRILL-2100
>             Project: Apache Drill
>          Issue Type: Bug
>          Components: Execution - Relational Operators
>    Affects Versions: 0.8.0
>            Reporter: Abhishek Girish
>            Assignee: Vitalii Diravka
>             Fix For: Future
>
>
> Currently, after forcing queries to use an external sort by switching off 
> hash join/agg causes spill-to-disk files accumulating. 
> This causes issues with disk space availability when the spill is configured 
> to be on the local file system (/tmp/drill). Also not optimal when configured 
> to use DFS (custom). 
> Drill must clean up all temporary files created after a query completes or 
> after a drillbit restart. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to