GitHub user CodingCat opened a pull request:
https://github.com/apache/spark/pull/2524
[SPARK-732][RESUBMIT] make if allowing duplicate update as an option of
accumulator
In current implementation, the accumulator will be updated for every
successfully finished task, even the task is from a resubmitted stage, which
makes the accumulator counter-intuitive
In this patch, I changed the way for the DAGScheduler to update the
accumulator,
DAGScheduler maintains a HashTable, mapping the stage id to the received
<accumulator_id , value> pairs. Only when the stage becomes independent, (no
job needs it any more), we accumulate the values of the <accumulator_id ,
value> pairs, when a task finished, we check if the HashTable has contained
such stageId, it saves the accumulator_id, value only when the task is the
first finished task of a new stage or the stage is running for the first
attempt...
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/CodingCat/spark SPARK-732-1
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/spark/pull/2524.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #2524
----
commit be10b9bf979226d2f9ac25ec902fe35a0f0ad0d0
Author: Nan Zhu <[email protected]>
Date: 2014-09-24T18:31:27Z
make if allowing duplicate update as an option of accumulator
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
