drill-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paul Rogers (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (DRILL-252) OOM setting MaxDirectMemory to 2gb
Date Sun, 18 Jun 2017 23:54:00 GMT

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

Mime
View raw message