You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Stefan Richter (JIRA)" <ji...@apache.org> on 2018/01/25 11:07:00 UTC

[jira] [Closed] (FLINK-7720) Centralize creation of backends and state related resources

     [ https://issues.apache.org/jira/browse/FLINK-7720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stefan Richter closed FLINK-7720.
---------------------------------
       Resolution: Fixed
    Fix Version/s: 1.5.0

Merged in 517b3f87214168a445b5751cda210ecf3a292fd6.

> Centralize creation of backends and state related resources
> -----------------------------------------------------------
>
>                 Key: FLINK-7720
>                 URL: https://issues.apache.org/jira/browse/FLINK-7720
>             Project: Flink
>          Issue Type: Improvement
>          Components: State Backends, Checkpointing
>    Affects Versions: 1.4.0
>            Reporter: Stefan Richter
>            Assignee: Stefan Richter
>            Priority: Major
>             Fix For: 1.5.0
>
>
> State related resources like keyed state backends, operator state backends, timer service manager, etc. are currently all created in different places, somewhere between {{StreamTask}} and {{AbstractStreamOperator}}. It is hard to identify where/how resources are created, which component owns them, and how certain components depend on others (e.g. there is only a timer service manager if there is also a keyed state backend).
> For the changes we plan for local state recovery, it would make sense to define a component that is responsible for the creation of state related resources and gives the possibility to interact in checkpointing and restoring with the checkpoint coordinator (owned by job manager) as well as local state storage (owned by task manager).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)