You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2023/07/01 06:03:00 UTC
[jira] [Updated] (FLINK-32496) Sources with idleness and alignment always wait for alignment when part of multiple sources is idle
[ https://issues.apache.org/jira/browse/FLINK-32496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
ASF GitHub Bot updated FLINK-32496:
-----------------------------------
Labels: pull-request-available (was: )
> Sources with idleness and alignment always wait for alignment when part of multiple sources is idle
> ---------------------------------------------------------------------------------------------------
>
> Key: FLINK-32496
> URL: https://issues.apache.org/jira/browse/FLINK-32496
> Project: Flink
> Issue Type: Bug
> Components: API / DataStream
> Affects Versions: 1.16.2, 1.17.1
> Reporter: haishui
> Assignee: Rui Fan
> Priority: Major
> Labels: pull-request-available
>
> Sources with idleness and alignment always wait for alignment when part of multiple sources is idle.
> *Root cause:*
> In [SourceOperator|https://github.com/apache/flink/blob/master/flink-streaming-java/src/main/java/org/apache/flink/streaming/api/operators/SourceOperator.java], `lastEmittedWatermark` is Long.MAX_VALUE if a source is idle.
> When other source is active, the `currentMaxDesiredWatermark` is less then Long.MAX_VALUE.
> So the `shouldWaitForAlignment` method is always true for idle sources.
>
> What's more, the source will become idle if a source wait for alignment for a long time, which also should be considered.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)