You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2019/02/22 10:32:00 UTC
[jira] [Updated] (FLINK-11723) Remove KvState related components
from NetworkEnvironment
[ https://issues.apache.org/jira/browse/FLINK-11723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
ASF GitHub Bot updated FLINK-11723:
-----------------------------------
Labels: pull-request-available (was: )
> Remove KvState related components from NetworkEnvironment
> ---------------------------------------------------------
>
> Key: FLINK-11723
> URL: https://issues.apache.org/jira/browse/FLINK-11723
> Project: Flink
> Issue Type: Sub-task
> Components: Network
> Reporter: zhijiang
> Assignee: zhijiang
> Priority: Minor
> Labels: pull-request-available
> Fix For: 1.9.0
>
>
> The {{NetworkEnvironment}} would be refactored into {{NetworkShuffleService}} created by {{ShuffleManager}} future. So the {{NetworkEnvironment}} should only cover shuffle related components to make the preparation.
> Currently {{KvStateRegistry}}, {{KvStateServer}}, {{KvStateClientProxy}} are not related to shuffle process and mainly used to be got in {{TaskExecutor}}. So it is reasonable to remove them from {{NetworkEnvironment}}.
> And then we could introduce a new {{KvStateService}} for wrapping these three components and pass it into {{TaskManagerService}}. This new service can also be passed into {{TaskExecutor,}} {{Task}} for use and avoid spreading in messy.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)