Hi Jacek, doesn't look like there is any good reason -- Mark Hamstra might know this best. Feel free to open a jira & pr for it, you can ping Mark, Kay Ousterhout, and me (@squito) for review.
Imran On Thu, Oct 13, 2016 at 7:56 AM, Jacek Laskowski <ja...@japila.pl> wrote: > Hi, > > Is there a reason why DAGScheduler.handleJobCancellation checks the > active job id in jobIdToStageIds [1] while looking the job up in > jobIdToActiveJob [2]? Perhaps synchronized earlier yet still > inconsistent. > > [1] https://github.com/apache/spark/blob/master/core/src/main/ > scala/org/apache/spark/scheduler/DAGScheduler.scala#L1372 > [2] https://github.com/apache/spark/blob/master/core/src/main/ > scala/org/apache/spark/scheduler/DAGScheduler.scala#L1376 > > Pozdrawiam, > Jacek Laskowski > ---- > https://medium.com/@jaceklaskowski/ > Mastering Apache Spark 2.0 https://bit.ly/mastering-apache-spark > Follow me at https://twitter.com/jaceklaskowski > > --------------------------------------------------------------------- > To unsubscribe e-mail: dev-unsubscr...@spark.apache.org > >
