GitHub user kl0u opened a pull request:

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

    [FLINK-6215] Make the StatefulSequenceSource scalable.

    So far this source was computing all the elements to
    be emitted and stored them in memory. This could lead
    to out-of-memory problems for large deployments. Now
    we split the range of elements into partitions that
    can be re-shuffled upon rescaling and we just store
    the next offset and the end of each one of them upon
    checkpointing.
    
    The current version of the PR has no backwards compatibility,
    as this becomes tricky given that we change the semantics
    of the state that we store.
    
    I believe that this is ok, given that it is a fix that has to go in
    the 1.3 and we are not sure if people are actually using it in 
    production, i.e. in settings that need backwards compatibility.
    
    What do you think @aljoscha @StephanEwen ?
    


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

    $ git pull https://github.com/kl0u/flink stateful-src

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

    https://github.com/apache/flink/pull/3669.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 #3669
    
----
commit cf333b0b0c318569a1704ca71121c37dcd12bd3d
Author: kl0u <kklou...@gmail.com>
Date:   2017-03-29T16:21:02Z

    [FLINK-6215] Make the StatefulSequenceSource scalable.
    
    So far this source was computing all the elements to
    be emitted and stored them in memory. This could lead
    to out-of-memory problems for large deployments. Now
    we do split the range of elements into partitions that
    can be re-shuffled upon rescaling and we just store
    the next offset and the end of each one of them upon
    checkpointing.

----


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

Reply via email to