Mailing-List: contact issues-help@drill.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@drill.apache.org
Date: Sun, 18 Jun 2017 23:54:00 +0000 (UTC)
From: "Paul Rogers (JIRA)" <jira@apache.org>
To: issues@drill.apache.org
Message-ID: <JIRA.12672877.1381261090000.43946.1497830040145@Atlassian.JIRA>
In-Reply-To: <JIRA.12672877.1381261090000@Atlassian.JIRA>
References: <JIRA.12672877.1381261090000@Atlassian.JIRA> <JIRA.12672877.1381261090795@jira-lw-us.apache.org>
Subject: [jira] [Resolved] (DRILL-252) OOM setting MaxDirectMemory to 2gb
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Sun, 18 Jun 2017 23:54:06 -0000


     [ https://issues.apache.org/jira/browse/DRILL-252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Paul Rogers resolved DRILL-252.
-------------------------------
    Resolution: Incomplete

Drill has since fixed many memory errors. No stack trace. Can't really track down this old bug, so closing.

> OOM setting MaxDirectMemory to 2gb
> ----------------------------------
>
>                 Key: DRILL-252
>                 URL: https://issues.apache.org/jira/browse/DRILL-252
>             Project: Apache Drill
>          Issue Type: Bug
>            Reporter: Timothy Chen
>            Priority: Minor
>             Fix For: Future
>
>
> I've deployed Drill to one node m1.medium and set DRILL_MAX_DIRECT_MEMORY to be 2048M, and running runbit I got a OOM in Direct memory allocation.
> Using 4gb resolves this problem, but I don't know what's the minimum requirement for Drill. If 4gb is the minimum ram required that perhaps we need to document this.
> Creating this as a bug as Jacques pointed we are not sure where we're needing that much space (or more of a runbit/env problem?)


--
This message was sent by Atlassian JIRA
(v6.4.14#64029)