flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From mxm <...@git.apache.org>
Subject [GitHub] flink pull request #2649: [FLINK-4829] snapshot accumulators on a best-effor...
Date Mon, 17 Oct 2016 12:41:47 GMT
GitHub user mxm opened a pull request:

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

    [FLINK-4829] snapshot accumulators on a best-effort basis

    Heartbeats should not fail when accumulators could not be snapshotted. Instead, we should
simply skip the reporting of the failed accumulator. Eventually, the accumulator will be reported;
at the latest, when the job finishes.

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

    $ git pull https://github.com/mxm/flink FLINK-4829

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

    https://github.com/apache/flink/pull/2649.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 #2649
    
----
commit 2a424a6120b7f1be8f357522a3fe964e77bd4cce
Author: Maximilian Michels <mxm@apache.org>
Date:   2016-10-14T13:15:50Z

    [FLINK-4829] protect user accumulators against concurrent updates

commit f162142b1d274895e16712e42f0f32a43e187db9
Author: Maximilian Michels <mxm@apache.org>
Date:   2016-10-17T12:19:00Z

    [FLINK-4829] snapshot accumulators on a best-effort basis
    
    Heartbeats should not fail when accumulators could not be snapshotted. Instead,
    we should simply skip the reporting of the failed accumulator. Eventually, the
    accumulator will be reported; at the latest, when the job finishes.

----


---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

Mime
View raw message