[
https://issues.apache.org/jira/browse/DRILL-7037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16766130#comment-16766130
]
Ayush Sharma commented on DRILL-7037:
-------------------------------------
The query works fine if used via JSON file , however that raises security
concerns for us as it is not secure in our project to use Disk space for
storing files (Also deleting is a concern in case our application crashes in
worst case scenario).
Also the query fails with sqlLine and JDBC client too (Crashes while still
running the planner).
Would like to understand what made Drill use this huge memory. It will be a
change in our architecture and we would have to search for an alternative if
Drill doesn't work with REST API call. So i am really looking forward to a
solution to this as it will be a big overhead to move away from this tool.
> 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
> Attachments: scheduler.txt
>
>
> 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)
