flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-7720) Centralize creation of backends and state related resources
Date Mon, 22 Jan 2018 13:11:00 GMT

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

ASF GitHub Bot commented on FLINK-7720:

Github user asfgit closed the pull request at:


> 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
> 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

View raw message