You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@spark.apache.org by "Xingbo Jiang (Jira)" <ji...@apache.org> on 2020/05/19 07:19:00 UTC

[jira] [Resolved] (SPARK-31651) Improve handling the case where different barrier sync types in a single sync

     [ https://issues.apache.org/jira/browse/SPARK-31651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Xingbo Jiang resolved SPARK-31651.
----------------------------------
    Fix Version/s: 3.0.0
       Resolution: Fixed

> Improve handling the case where different barrier sync types in a single sync
> -----------------------------------------------------------------------------
>
>                 Key: SPARK-31651
>                 URL: https://issues.apache.org/jira/browse/SPARK-31651
>             Project: Spark
>          Issue Type: Improvement
>          Components: Spark Core
>    Affects Versions: 3.0.0
>            Reporter: wuyi
>            Assignee: wuyi
>            Priority: Major
>             Fix For: 3.0.0
>
>
> Currently, we use cleanupBarrierStage when detecting different barrier sync types in a single sync. This cause a problem that a new `ContextBarrierState` can be created again if there's following requesters on the way. And those corresponding tasks will fail because of killing instead of different barrier sync types detected.
>  
>  



--
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