[
https://issues.apache.org/jira/browse/DRILL-7037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16766837#comment-16766837
]
Ayush Sharma commented on DRILL-7037:
-------------------------------------
[~priteshm] [~vitalii] Please find the details below:
Request Body : {\"queryType\" : \"SQL\",\"query\" : \"**QUERY**"}
*'QUERY'* - select e.* from (select FLATTEN(t.jdata) from ((select
convert_from('<*our json*>','json') as jdata) UNION ALL (select
convert_from('<*our json*>','json') as jdata)) t) e
*'our json' -* Because of the string limit we are appending the query one by
one to be within the string limit imposed by Drill on command line or REST Call
(Not sure of the exact value , approx 20000 chars)
Please do let me know if you need anything else to debug the issue.
*Out of Memory Exception:*
----
{code:java}
// Catastrophic failure occurred. Exiting. Information follows: Unable to
handle out of memory condition in Foreman.
java.lang.OutOfMemoryError: Java heap space
at java.util.Arrays.copyOf(Arrays.java:3332)
at
java.lang.AbstractStringBuilder.ensureCapacityInternal(AbstractStringBuilder.java:124)
at java.lang.AbstractStringBuilder.append(AbstractStringBuilder.java:448)
at java.lang.StringBuffer.append(StringBuffer.java:270)
at java.io.StringWriter.write(StringWriter.java:112)
at java.io.PrintWriter.write(PrintWriter.java:456)
at java.io.PrintWriter.write(PrintWriter.java:473)
at org.apache.calcite.rel.AbstractRelNode$1.explain_(AbstractRelNode.java:415)
at org.apache.calcite.rel.externalize.RelWriterImpl.done(RelWriterImpl.java:156)
at org.apache.calcite.rel.AbstractRelNode.explain(AbstractRelNode.java:314)
at
org.apache.calcite.rel.AbstractRelNode.computeDigest(AbstractRelNode.java:422)
at
org.apache.calcite.rel.AbstractRelNode.recomputeDigest(AbstractRelNode.java:358)
at org.apache.calcite.rel.core.SetOp.replaceInput(SetOp.java:89)
at org.apache.calcite.plan.hep.HepPlanner.buildFinalPlan(HepPlanner.java:878)
at org.apache.calcite.plan.hep.HepPlanner.buildFinalPlan(HepPlanner.java:877)
at org.apache.calcite.plan.hep.HepPlanner.buildFinalPlan(HepPlanner.java:877)
at org.apache.calcite.plan.hep.HepPlanner.buildFinalPlan(HepPlanner.java:877)
at org.apache.calcite.plan.hep.HepPlanner.buildFinalPlan(HepPlanner.java:877)
at org.apache.calcite.plan.hep.HepPlanner.buildFinalPlan(HepPlanner.java:877)
at org.apache.calcite.plan.hep.HepPlanner.buildFinalPlan(HepPlanner.java:877)
at org.apache.calcite.plan.hep.HepPlanner.buildFinalPlan(HepPlanner.java:877)
at org.apache.calcite.plan.hep.HepPlanner.buildFinalPlan(HepPlanner.java:877)
at org.apache.calcite.plan.hep.HepPlanner.buildFinalPlan(HepPlanner.java:877)
at org.apache.calcite.plan.hep.HepPlanner.buildFinalPlan(HepPlanner.java:877)
at org.apache.calcite.plan.hep.HepPlanner.buildFinalPlan(HepPlanner.java:877)
at org.apache.calcite.plan.hep.HepPlanner.buildFinalPlan(HepPlanner.java:877)
at org.apache.calcite.plan.hep.HepPlanner.buildFinalPlan(HepPlanner.java:877)
at org.apache.calcite.plan.hep.HepPlanner.buildFinalPlan(HepPlanner.java:877)
at org.apache.calcite.plan.hep.HepPlanner.buildFinalPlan(HepPlanner.java:877)
at org.apache.calcite.plan.hep.HepPlanner.buildFinalPlan(HepPlanner.java:877)
at org.apache.calcite.plan.hep.HepPlanner.buildFinalPlan(HepPlanner.java:877)
at org.apache.calcite.plan.hep.HepPlanner.buildFinalPlan(HepPlanner.java:877)
{code}
> Apache Drill Crashes when a 50mb json string is queried via the REST API
> provided
> ---------------------------------------------------------------------------------
>
> Key: DRILL-7037
> URL: https://issues.apache.org/jira/browse/DRILL-7037
> Project: Apache Drill
> Issue Type: Bug
> Components: Client - HTTP
> Affects Versions: 1.14.0
> Environment: Windows 10
> 24GB RAM
> 8 Cores
> Used the REST API call to query drill
> Reporter: Ayush Sharma
> Priority: Blocker
>
> Apache Drill crashes with OutofMemoryException (24GB RAM) when a REST API
> call is made by supplying a json of size 50MB in the query paramater of the
> REST API.
> The REST API even crashes for a 10MB query (16GB RAM) and works with a 5MB
> query.
> This is a blocker for us and will need immediate remediation.
> We are also not aware of any sys.options which might bring the HEAP size down
> drastically or currently making it go up.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
