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/02/15 08:02:00 UTC

[jira] [Commented] (FLINK-31080) Idle slots are not released due to a mismatch in time between DeclarativeSlotPoolService and SlotSharingSlotAllocator

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

Weijie Guo commented on FLINK-31080:
------------------------------------

Ahh, this may indeed be a problem. Thanks [~prabhujoseph] for reporting this. 

> Idle slots are not released due to a mismatch in time between DeclarativeSlotPoolService and SlotSharingSlotAllocator
> ---------------------------------------------------------------------------------------------------------------------
>
>                 Key: FLINK-31080
>                 URL: https://issues.apache.org/jira/browse/FLINK-31080
>             Project: Flink
>          Issue Type: Bug
>    Affects Versions: 1.16.1
>            Reporter: Prabhu Joseph
>            Priority: Major
>
> Due to a timing mismatch between {{DeclarativeSlotPoolService}} and {{{}SlotSharingSlotAllocator{}}}, idle slots are not released.
> {{DeclarativeSlotPoolService}} uses {{{}SystemClock#relativeTimeMillis{}}}, i.e., {{{}System.nanoTime{}}}() / 1_000_000, while offering a slot, whereas {{SlotSharingSlotAllocator}} uses {{{}System.currentTimeMillis{}}}() while freeing the reserved slot. 
> The idle timeout check fails wrongly as "{{{}System.currentTimeMillis(){}}}" will have a very high value compared to "{{{}SystemClock#relativeTimeMillis{}}}".



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