Mailing-List: contact issues-help@spark.apache.org; run by ezmlm
Precedence: bulk
Date: Thu, 20 Apr 2017 13:59:05 +0000 (UTC)
From: "Sean Owen (JIRA)" <jira@apache.org>
To: issues@spark.apache.org
Message-ID: <JIRA.13065425.1492673370000.6337.1492696745958@Atlassian.JIRA>
In-Reply-To: <JIRA.13065425.1492673370000@Atlassian.JIRA>
References: <JIRA.13065425.1492673370000@Atlassian.JIRA> <JIRA.13065425.1492673370242@jira-lw-us.apache.org>
Subject: [jira] [Commented] (SPARK-20404) Regression with accumulator names
 when migrating from 1.6 to 2.x
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Thu, 20 Apr 2017 13:59:14 -0000


    [ https://issues.apache.org/jira/browse/SPARK-20404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15976732#comment-15976732 ] 

Sean Owen commented on SPARK-20404:
-----------------------------------

We use pull requests, not patches. See http://spark.apache.org/contributing.html

> Regression with accumulator names when migrating from 1.6 to 2.x
> ----------------------------------------------------------------
>
>                 Key: SPARK-20404
>                 URL: https://issues.apache.org/jira/browse/SPARK-20404
>             Project: Spark
>          Issue Type: Bug
>          Components: Spark Core
>    Affects Versions: 2.0.0, 2.0.1, 2.0.2, 2.1.0
>         Environment: Spark: 2.1
> Scala: 2.11
> Spark master: local
>            Reporter: Sergey Zhemzhitsky
>         Attachments: spark-context-accum-option.patch
>
>
> Creating accumulator with explicitly specified name equal to _null_, like the following
> {code:java}
> sparkContext.accumulator(0, null)
> {code}
> throws exception at runtime
> {code:none}
> ERROR | DAGScheduler | dag-scheduler-event-loop | Failed to update accumulators for task 0
> java.lang.NullPointerException
> 	at org.apache.spark.util.AccumulatorV2$$anonfun$1.apply(AccumulatorV2.scala:106)
> 	at org.apache.spark.util.AccumulatorV2$$anonfun$1.apply(AccumulatorV2.scala:106)
> 	at scala.Option.exists(Option.scala:240)
> 	at org.apache.spark.util.AccumulatorV2.toInfo(AccumulatorV2.scala:106)
> 	at org.apache.spark.scheduler.DAGScheduler$$anonfun$updateAccumulators$1.apply(DAGScheduler.scala:1091)
> 	at org.apache.spark.scheduler.DAGScheduler$$anonfun$updateAccumulators$1.apply(DAGScheduler.scala:1080)
> 	at scala.collection.mutable.ResizableArray$class.foreach(ResizableArray.scala:59)
> 	at scala.collection.mutable.ArrayBuffer.foreach(ArrayBuffer.scala:48)
> 	at org.apache.spark.scheduler.DAGScheduler.updateAccumulators(DAGScheduler.scala:1080)
> 	at org.apache.spark.scheduler.DAGScheduler.handleTaskCompletion(DAGScheduler.scala:1183)
> 	at org.apache.spark.scheduler.DAGSchedulerEventProcessLoop.doOnReceive(DAGScheduler.scala:1647)
> 	at org.apache.spark.scheduler.DAGSchedulerEventProcessLoop.onReceive(DAGScheduler.scala:1605)
> 	at org.apache.spark.scheduler.DAGSchedulerEventProcessLoop.onReceive(DAGScheduler.scala:1594)
> 	at org.apache.spark.util.EventLoop$$anon$1.run(EventLoop.scala:48)
> {code}
> The issue is in wrapping name into _Some_ instead of _Option_ when creating accumulators.
> Patch is available.


--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org