You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Marcelo Vanzin (JIRA)" <ji...@apache.org> on 2018/01/31 19:50:00 UTC
[jira] [Resolved] (SPARK-21525) ReceiverSupervisorImpl seems to
ignore the error code when writing to the WAL
[ https://issues.apache.org/jira/browse/SPARK-21525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marcelo Vanzin resolved SPARK-21525.
------------------------------------
Resolution: Fixed
Fix Version/s: 2.4.0
> ReceiverSupervisorImpl seems to ignore the error code when writing to the WAL
> -----------------------------------------------------------------------------
>
> Key: SPARK-21525
> URL: https://issues.apache.org/jira/browse/SPARK-21525
> Project: Spark
> Issue Type: Bug
> Components: DStreams
> Affects Versions: 2.2.0
> Reporter: Mark Grover
> Assignee: Marcelo Vanzin
> Priority: Major
> Fix For: 2.4.0
>
>
> {{AddBlock}} returns an error code related to whether writing the block to the WAL was successful or not. In cases where a WAL may be unavailable temporarily, the write would fail but it seems like we are not using the return code (see [here|https://github.com/apache/spark/blob/ba8912e5f3d5c5a366cb3d1f6be91f2471d048d2/streaming/src/main/scala/org/apache/spark/streaming/receiver/ReceiverSupervisorImpl.scala#L162]).
> For example, when using the Flume Receiver, we should be sending a n'ack back to Flume if the block wasn't written to the WAL. I haven't gone through the full code path yet but at least from looking at the ReceiverSupervisorImpl, it doesn't seem like that return code is being used.
--
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