You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Mridul Muralidharan (Jira)" <ji...@apache.org> on 2021/08/16 19:02:00 UTC
[jira] [Resolved] (SPARK-35548) Handling new attempt has started
error message in BlockPushErrorHandler in client
[ https://issues.apache.org/jira/browse/SPARK-35548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mridul Muralidharan resolved SPARK-35548.
-----------------------------------------
Fix Version/s: 3.2.0
Resolution: Fixed
Issue resolved by pull request 33617
[https://github.com/apache/spark/pull/33617]
> Handling new attempt has started error message in BlockPushErrorHandler in client
> ---------------------------------------------------------------------------------
>
> Key: SPARK-35548
> URL: https://issues.apache.org/jira/browse/SPARK-35548
> Project: Spark
> Issue Type: Sub-task
> Components: Shuffle, Spark Core
> Affects Versions: 3.1.0
> Reporter: Ye Zhou
> Priority: Major
> Fix For: 3.2.0
>
>
> In SPARK-33350, a new type of error message is introduced in BlockPushErrorHandler which indicates the PushblockStream message is received after a new application attempt has started. This error message should be correctly handled in client without retrying the block push.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org