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-4556) Make Queryable State Key-Group Aware
Date Fri, 23 Sep 2016 12:03:20 GMT

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

ASF GitHub Bot commented on FLINK-4556:

Github user asfgit closed the pull request at:


> Make Queryable State Key-Group Aware
> ------------------------------------
>                 Key: FLINK-4556
>                 URL: https://issues.apache.org/jira/browse/FLINK-4556
>             Project: Flink
>          Issue Type: Bug
>          Components: Streaming
>    Affects Versions: 1.2.0
>            Reporter: Aljoscha Krettek
>            Assignee: Stefan Richter
>            Priority: Blocker
> The recent introduction of key-grouped state breaks queryable state because the JobManager
does not yet forward the client to the correct TaskManager based on key-group ranges.
> This will either have to be implemented on the JobManager side, i.e. in {{AkkaKvStateLocationLookupService}}
or on the {{TaskManager}} when state is registered. The JobManager can know the mapping because
it should know the {{parallelism}}/{{maxParallelism}} which it can use to determine where
the state for a key-group is stored. The {{TaskManager}} send a {{NotifyKvStateRegistered}}
message that already contains a {{keyGroupIndex}} field that is not useful/correct at the
moment, though.

This message was sent by Atlassian JIRA

View raw message