You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Lijie Wang (Jira)" <ji...@apache.org> on 2022/01/17 08:05:00 UTC

[jira] [Updated] (FLINK-25033) Let some scheduler components updatable

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

Lijie Wang updated FLINK-25033:
-------------------------------
    Description: 
Many scheduler components rely on the execution topology to make decisions. Some of them will build up some mappings against the execution topology on initialization for later use. When the execution topology becomes dynamic, these components need to be notified about the topology changes and adjust themselves accordingly. These components are:
 * DefaultExecutionTopology
 * SchedulingStrategy
 * PartitionReleaseStrategy
 * SlotSharingStrategy

  was:
Many scheduler components rely on the execution topology to make decisions. Some of them will build up some mappings against the execution topology on initialization for later use. When the execution topology becomes dynamic, these components need to be notified about the topology changes and adjust themselves accordingly. These components are:
 * DefaultExecutionTopology
 * SchedulingStrategy
 * PartitionReleaseStrategy
 * SlotSharingStrategy
 * OperatorCoordinatorHandler
 * Network memory of SlotSharingGroup.


> Let some scheduler components updatable
> ---------------------------------------
>
>                 Key: FLINK-25033
>                 URL: https://issues.apache.org/jira/browse/FLINK-25033
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Runtime / Coordination
>            Reporter: Lijie Wang
>            Assignee: Lijie Wang
>            Priority: Major
>              Labels: pull-request-available
>
> Many scheduler components rely on the execution topology to make decisions. Some of them will build up some mappings against the execution topology on initialization for later use. When the execution topology becomes dynamic, these components need to be notified about the topology changes and adjust themselves accordingly. These components are:
>  * DefaultExecutionTopology
>  * SchedulingStrategy
>  * PartitionReleaseStrategy
>  * SlotSharingStrategy



--
This message was sent by Atlassian Jira
(v8.20.1#820001)