You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@flink.apache.org by "Mason Chen (Jira)" <ji...@apache.org> on 2022/05/03 07:46:00 UTC

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

Mason Chen created FLINK-27479:
----------------------------------

             Summary: HybridSource refreshes availability future
                 Key: FLINK-27479
                 URL: https://issues.apache.org/jira/browse/FLINK-27479
             Project: Flink
          Issue Type: Improvement
          Components: Connectors / Common
    Affects Versions: 1.14.4
            Reporter: Mason Chen
             Fix For: 1.15.1


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)