You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "RocMarshal (Jira)" <ji...@apache.org> on 2024/10/04 15:20:00 UTC
[jira] (FLINK-36426) Introduce the strategy for adaptive scheduler to control state locality preferred or minimal task executors preferred when matching resource requests and slots
[ https://issues.apache.org/jira/browse/FLINK-36426 ]
RocMarshal deleted comment on FLINK-36426:
------------------------------------
was (Author: rocmarshal):
as discussed in [https://github.com/apache/flink/pull/25218#discussion_r1771187666]
jobmanager.adaptive-scheduler.state-locality-minimum-taskmanagers-preferred:
the type is boolean
the default value is false
When the value is true, the scheduler will prioritize selecting the least TM, followed by maximizing compatibility with state-locality for slot allocation
When the value is false, the scheduler will prioritize allocating slots based on the maximum state-locality without considering whether the occupied TM can be released
And I'm willing to do contribute for it if possible (eg. driving a email for discussing the parameters ... etc.) ~ :)
Looking forward the discussion related~ many thx!
> Introduce the strategy for adaptive scheduler to control state locality preferred or minimal task executors preferred when matching resource requests and slots
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: FLINK-36426
> URL: https://issues.apache.org/jira/browse/FLINK-36426
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Coordination
> Reporter: RocMarshal
> Priority: Major
>
> as discussed in [https://github.com/apache/flink/pull/25218#discussion_r1771187666]
> jobmanager.adaptive-scheduler.state-locality-minimum-taskmanagers-preferred:
> the type is boolean
> the default value is false
> When the value is true, the scheduler will prioritize selecting the least TM, followed by maximizing compatibility with state-locality for slot allocation
> When the value is false, the scheduler will prioritize allocating slots based on the maximum state-locality without considering whether the occupied TM can be released
> And I'm willing to do contribute for it if possible (eg. driving a email for discussing the parameters ... etc.) ~ :)
> Looking forward the discussion related~ many thx!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)