You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Reynold Xin (JIRA)" <ji...@apache.org> on 2015/06/01 23:05:20 UTC
[jira] [Comment Edited] (SPARK-8008) sqlContext.jdbc can kill your
database due to high concurrency
[ https://issues.apache.org/jira/browse/SPARK-8008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14567999#comment-14567999 ]
Reynold Xin edited comment on SPARK-8008 at 6/1/15 9:04 PM:
------------------------------------------------------------
Batching everything into giant partitions have downsides w.r.t. fault tolerance, memory consumption, etc. I wouldn't call this a super high priority, but if somebody works on a patch we should merge it.
was (Author: rxin):
Batching everything into giant partitions have pretty downsides w.r.t. fault tolerance, memory consumption, etc. I wouldn't call this a super high priority, but if somebody works on a patch we should merge it.
> sqlContext.jdbc can kill your database due to high concurrency
> --------------------------------------------------------------
>
> Key: SPARK-8008
> URL: https://issues.apache.org/jira/browse/SPARK-8008
> Project: Spark
> Issue Type: Bug
> Reporter: Rene Treffer
>
> Spark tries to load as many partitions as possible in parallel, which can in turn overload the database although it would be possible to load all partitions given a lower concurrency.
> It would be nice to either limit the maximum concurrency or to at least warn about this behavior.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org