[ https://issues.apache.org/jira/browse/SPARK-3628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14222672#comment-14222672 ]
Patrick Wendell commented on SPARK-3628: ---------------------------------------- I took a quick look at the current patch and i'm re-assigning the target version to 1.2.1. From what I can tell this involves nontrivial changes to the DAGScheduler. That's too critical of a component to modify substantially without significant testing. Let's try to get a fix into master and then put it into 1.2.1. down the road. > Don't apply accumulator updates multiple times for tasks in result stages > ------------------------------------------------------------------------- > > Key: SPARK-3628 > URL: https://issues.apache.org/jira/browse/SPARK-3628 > Project: Spark > Issue Type: Bug > Reporter: Matei Zaharia > Assignee: Nan Zhu > Priority: Blocker > > In previous versions of Spark, accumulator updates only got applied once for > accumulators that are only used in actions (i.e. result stages), letting you > use them to deterministically compute a result. Unfortunately, this got > broken in some recent refactorings. > This is related to https://issues.apache.org/jira/browse/SPARK-732, but that > issue is about applying the same semantics to intermediate stages too, which > is more work and may not be what we want for debugging. -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org For additional commands, e-mail: issues-h...@spark.apache.org