[
https://issues.apache.org/jira/browse/DRILL-252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14094905#comment-14094905
]
Venkata krishnan Sowrirajan commented on DRILL-252:
---------------------------------------------------
I also got the same error, when I queried a hive table for 100k records, saying
OutOfMemory Error at Direct Memory Buffer. But the maxDirectMemory was set to
4G. Increasing it to 16G, solved the problem. I guess even with 8G of
maxDirectMemory, I am still hitting the problem.
> 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
> 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.2#6252)
