You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Weijie Guo (Jira)" <ji...@apache.org> on 2023/04/25 07:44:00 UTC
[jira] [Closed] (FLINK-31842) calculate task executor's utilization only in EvenlySpreadOutLocationPreferenceSlotSelectionStrategy
[ https://issues.apache.org/jira/browse/FLINK-31842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Weijie Guo closed FLINK-31842.
------------------------------
Fix Version/s: 1.18.0
Resolution: Fixed
master(1.18) via fa053e3f1f3b7317d7b9dfbf91d7f4accc50b100.
> calculate task executor's utilization only in EvenlySpreadOutLocationPreferenceSlotSelectionStrategy
> ----------------------------------------------------------------------------------------------------
>
> Key: FLINK-31842
> URL: https://issues.apache.org/jira/browse/FLINK-31842
> Project: Flink
> Issue Type: Sub-task
> Components: Runtime / Coordination
> Reporter: Weihua Hu
> Assignee: Weihua Hu
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.18.0
>
>
> Currently DefaultAllocatedSlotPool#getFreeSlotsInformation always calculates the taskExecutorUtilization. This causes task schedules to be too slow when there are lots of slots, such as 20000 slots total. But only the EvenlySpreadOutLocationPreferenceSlotSelectionStrategy uses this utilization.
> So I would like to move the calculation of taskExecutorUtilization to usage. DefaultAllocatedSlotPool provides a function: getTaskExecutorUtilization, and is only used in EvenlySpreadOutLocationPreferenceSlotSelectionStrategy.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)