Mailing-List: contact issues-help@drill.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@drill.incubator.apache.org
Date: Wed, 11 Jun 2014 07:47:01 +0000 (UTC)
From: "Steven Phillips (JIRA)" <jira@apache.org>
To: issues@drill.incubator.apache.org
Message-ID: <JIRA.12709208.1397795556156.107598.1402472821745@arcas>
In-Reply-To: <JIRA.12709208.1397795556156@arcas>
References: <JIRA.12709208.1397795556156@arcas>
Subject: [jira] [Commented] (DRILL-544) DrillBit is un-responsive after a
 query with multiple joins is executed repeatedly
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ 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)