You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Cheng Lian (JIRA)" <ji...@apache.org> on 2014/08/28 02:56:57 UTC
[jira] [Updated] (SPARK-3269)
SparkSQLOperationManager.getNextRowSet OOMs when a large maxRows is set
[ https://issues.apache.org/jira/browse/SPARK-3269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Cheng Lian updated SPARK-3269:
------------------------------
Description: {{SparkSQLOperationManager.getNextRowSet}} allocates an {{ArrayBuffer[Row]}} as large as {{maxRows}}, which can lead to OOM if {{maxRows}} is large, even if the actual size of the row set is much smaller. (was: {{SparkSQLOperationManager.getNextRowSet}} allocates an {{ArrayBuffer[Row]}} as large as {{maxRows}}, which can lead to OOM if {{maxRows}} is large.)
> SparkSQLOperationManager.getNextRowSet OOMs when a large maxRows is set
> -----------------------------------------------------------------------
>
> Key: SPARK-3269
> URL: https://issues.apache.org/jira/browse/SPARK-3269
> Project: Spark
> Issue Type: Bug
> Components: SQL
> Affects Versions: 1.0.2
> Reporter: Cheng Lian
>
> {{SparkSQLOperationManager.getNextRowSet}} allocates an {{ArrayBuffer[Row]}} as large as {{maxRows}}, which can lead to OOM if {{maxRows}} is large, even if the actual size of the row set is much smaller.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org