You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Hyukjin Kwon (JIRA)" <ji...@apache.org> on 2019/05/21 04:34:45 UTC
[jira] [Resolved] (SPARK-17539) Streaming Backpressure Starves
DirectStream When Used In Combination With Receivers
[ https://issues.apache.org/jira/browse/SPARK-17539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hyukjin Kwon resolved SPARK-17539.
----------------------------------
Resolution: Incomplete
> Streaming Backpressure Starves DirectStream When Used In Combination With Receivers
> -----------------------------------------------------------------------------------
>
> Key: SPARK-17539
> URL: https://issues.apache.org/jira/browse/SPARK-17539
> Project: Spark
> Issue Type: Bug
> Components: DStreams
> Affects Versions: 1.5.0
> Environment: Spark 1.5.0 under CDH 5.5.1 w/ Kafka 0.8.2.1
> Reporter: Jeff Nadler
> Priority: Major
> Labels: bulk-closed
>
> Backpressure seems to work fine for Direct Streams when used alone.
> We use Receivers (x4) to consume Topic A, and a Direct Stream to consume Topic B in a single Streaming app. Both go through updateStateByKey and are later joined.
> In this configuration, backpressure works as expected for the Receivers but not for the Direct Stream. After running for some time there is no scheduling delay - there is some at startup, but it burns off in a minute or two.
> The Direct Stream will get 'stuck' throttled at 1 msg / partition / sec. As soon as I turn off backpressure this problem goes away.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org