You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2015/04/04 10:43:33 UTC

[jira] [Commented] (FLINK-951) Reworking of Iteration Synchronization, Accumulators and Aggregators

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

ASF GitHub Bot commented on FLINK-951:
--------------------------------------

GitHub user markus-h opened a pull request:

    https://github.com/apache/flink/pull/570

    [FLINK-951] Reworking of Iteration Synchronization, Accumulators and Aggregators

    Iteration synchronization through JobManager
    Unification of Accumulators and Aggregators (removal of former Aggregators)
    Adjusted testcases accordingly
    
    I redid the work of my very old pull request https://github.com/apache/flink/pull/36
    A more detailed description can be found in jira https://issues.apache.org/jira/browse/FLINK-951
    
    I came across some unexpected behaviour with akka that made a small hack neccessary. Perhaps somebody with more experience in akka can find a better solution. See IterationHeadPactTask line 392.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/markus-h/incubator-flink iterationsAndAccumulatorsRework2

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/flink/pull/570.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 #570
    
----
commit 5492487892ff99f10fccdb075404dedaa3371ff7
Author: Markus Holzemer <ma...@gmx.de>
Date:   2015-04-02T15:56:19Z

    Iteration synchronization through JobManager
    Unification of Accumulators and Aggregators (removal of former Aggregators)
    Adjusted testcases accordingly

----


> Reworking of Iteration Synchronization, Accumulators and Aggregators
> --------------------------------------------------------------------
>
>                 Key: FLINK-951
>                 URL: https://issues.apache.org/jira/browse/FLINK-951
>             Project: Flink
>          Issue Type: Improvement
>          Components: Iterations, Optimizer
>    Affects Versions: 0.6-incubating
>            Reporter: Markus Holzemer
>            Assignee: Markus Holzemer
>              Labels: refactoring
>   Original Estimate: 168h
>  Remaining Estimate: 168h
>
> I just realized that there is no real Jira issue for the task I am currently working on. 
> I am currently reworking a few things regarding Iteration Synchronization, Accumulators and Aggregators. Currently the synchronization at the end of one superstep is done through channel events. That makes it hard to track the current status of iterations. That is why I am changing this synchronization to use RPC calls with the JobManager, so that the JobManager manages the current status of all iterations.
> Currently we use Accumulators outside of iterations and Aggregators inside of iterations. Both have a similiar function, but a bit different interfaces and handling. I want to unify these two concepts. I propose that we stick in the future to Accumulators only. Aggregators therefore are removed and Accumulators are extended to cover the usecases Aggregators were used fore before. The switch to RPC for iterations makes it possible to also send the current Accumulator values at the end of each superstep, so that the JobManager (and thereby the webinterface) will be able to print intermediate accumulation results.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)