You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Michael Armbrust (JIRA)" <ji...@apache.org> on 2015/06/01 14:09:17 UTC
[jira] [Commented] (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=14567219#comment-14567219 ]
Michael Armbrust commented on SPARK-8008:
-----------------------------------------
I'm okay adding documentation about this behavior where ever you think it would help, but I would say this is "by design".
I'd suggest that if you want lower concurrency use fewer partitions to extract the data and then {{repartition}} if you need higher concurrency for subsequent operations.
> 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