You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "David Anderson (Jira)" <ji...@apache.org> on 2022/06/15 12:56:00 UTC

[jira] [Updated] (FLINK-27479) HybridSource refreshes availability future

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

David Anderson updated FLINK-27479:
-----------------------------------
    Fix Version/s: 1.15.2
                       (was: 1.15.1)

> HybridSource refreshes availability future
> ------------------------------------------
>
>                 Key: FLINK-27479
>                 URL: https://issues.apache.org/jira/browse/FLINK-27479
>             Project: Flink
>          Issue Type: Bug
>          Components: Connectors / Common
>    Affects Versions: 1.14.4
>            Reporter: Mason Chen
>            Assignee: Mason Chen
>            Priority: Major
>             Fix For: 1.15.2
>
>
> HybridSourceReader needs to refresh the availability future according to the underlying reader. It currently maintains its own future and completes it after the sub-reader's availability future is complete. However, the implementation does not refresh the future again until the reader receives a switch event. This can cause a tight loop with the Flink runtime repeatedly invoking pollNext() and high CPU utilization.
>  
> To solve this, we can reuse the MultipleFuturesAvailabilityHelper to manage the lifecycle of the availability future.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)