You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@drill.apache.org by "Steven Phillips (JIRA)" <ji...@apache.org> on 2014/06/11 09:47:01 UTC
[jira] [Commented] (DRILL-544) DrillBit is un-responsive after a
query with multiple joins is executed repeatedly
[ https://issues.apache.org/jira/browse/DRILL-544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14027519#comment-14027519 ]
Steven Phillips commented on DRILL-544:
---------------------------------------
I think this is fixed.
Are you still seeing this?
> DrillBit is un-responsive after a query with multiple joins is executed repeatedly
> ----------------------------------------------------------------------------------
>
> Key: DRILL-544
> URL: https://issues.apache.org/jira/browse/DRILL-544
> Project: Apache Drill
> Issue Type: Bug
> Components: Execution - Flow
> Environment: Centos 6.4
> 96GB RAM
> Reporter: Kunal Khatua
> Assignee: Steven Phillips
> Fix For: 1.0.0-BETA1
>
>
> When running a query against a standalone DrillBit with default settings, every run of a query with joins results in the memory for the DrillBit process increasing. This occurs, irrespective of whether the query runs to completion or not.
> After a number of runs, the DrillBit becomes unresponsive, with no CPU activity visible with the top command.
--
This message was sent by Atlassian JIRA
(v6.2#6252)