[jira] [Updated] (DRILL-6477) Drillbit hangs/crashes with OOME Java Heap Space for a large query through WebUI
[ https://issues.apache.org/jira/browse/DRILL-6477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pritesh Maker updated DRILL-6477: - Labels: ready-to-commit (was: ) > Drillbit hangs/crashes with OOME Java Heap Space for a large query through > WebUI > > > Key: DRILL-6477 > URL: https://issues.apache.org/jira/browse/DRILL-6477 > Project: Apache Drill > Issue Type: Bug > Components: Web Server >Affects Versions: 1.13.0 >Reporter: Kunal Khatua >Assignee: Kunal Khatua >Priority: Major > Labels: ready-to-commit > Fix For: 1.14.0 > > > For queries submitted through the WebUI and retrieving a large resultset, the > Drillbit often hangs or crashes due to the (foreman) Drillbit running out of > Heap memory. > This is because the Web client translates the resultset into a massive object > in the heap-space and tries to send that back to the browser. This results in > the VM thread actively trying to perform GC if the memory is not sufficient. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (DRILL-6477) Drillbit hangs/crashes with OOME Java Heap Space for a large query through WebUI
[ https://issues.apache.org/jira/browse/DRILL-6477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pritesh Maker updated DRILL-6477: - Remaining Estimate: (was: 48h) Original Estimate: (was: 48h) > Drillbit hangs/crashes with OOME Java Heap Space for a large query through > WebUI > > > Key: DRILL-6477 > URL: https://issues.apache.org/jira/browse/DRILL-6477 > Project: Apache Drill > Issue Type: Bug > Components: Web Server >Affects Versions: 1.13.0 >Reporter: Kunal Khatua >Assignee: Kunal Khatua >Priority: Major > Labels: ready-to-commit > Fix For: 1.14.0 > > > For queries submitted through the WebUI and retrieving a large resultset, the > Drillbit often hangs or crashes due to the (foreman) Drillbit running out of > Heap memory. > This is because the Web client translates the resultset into a massive object > in the heap-space and tries to send that back to the browser. This results in > the VM thread actively trying to perform GC if the memory is not sufficient. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
