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

Matthias Pohl commented on FLINK-34588:
---------------------------------------

cc [~huwh]

> FineGrainedSlotManager checks whether resources need to reconcile but doesn't 
> act on the result
> -----------------------------------------------------------------------------------------------
>
>                 Key: FLINK-34588
>                 URL: https://issues.apache.org/jira/browse/FLINK-34588
>             Project: Flink
>          Issue Type: Bug
>          Components: Runtime / Coordination
>    Affects Versions: 1.19.0, 1.18.1, 1.20.0
>            Reporter: Matthias Pohl
>            Priority: Major
>
> There are a few locations in {{FineGrainedSlotManager}} where we check 
> whether resources can/need to be reconciled but don't care about the result 
> and just trigger the resource update (e.g. in 
> [FineGrainedSlotManager:620|https://github.com/apache/flink/blob/c0d3e495f4c2316a80f251de77b05b943b5be1f8/flink-runtime/src/main/java/org/apache/flink/runtime/resourcemanager/slotmanager/FineGrainedSlotManager.java#L620]
>  and 
> [FineGrainedSlotManager:676|https://github.com/apache/flink/blob/c0d3e495f4c2316a80f251de77b05b943b5be1f8/flink-runtime/src/main/java/org/apache/flink/runtime/resourcemanager/slotmanager/FineGrainedSlotManager.java#L676]).
>  Looks like we could reduce the calls to the backend here.
> It's not having a major impact because this feature is only used in the 
> {{ActiveResourceManager}} which triggers 
> [checkResourceDeclarations|https://github.com/apache/flink/blob/c678244a3890273145a786b9e1bf1a4f96f6dcfd/flink-runtime/src/main/java/org/apache/flink/runtime/resourcemanager/active/ActiveResourceManager.java#L331]
>  and reevaluates the {{resourceDeclarations}}. Not sure whether I missed 
> something here and there's actually a bigger issue with it. But considering 
> that nobody complained about it in the past, I'd assume that it's not a 
> severe issue.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to