You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Yun Gao (Jira)" <ji...@apache.org> on 2022/04/13 06:28:04 UTC

[jira] [Updated] (FLINK-20305) Iterative job with maxWaitTimeMillis does not terminate

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

Yun Gao updated FLINK-20305:
----------------------------
    Fix Version/s: 1.16.0

> Iterative job with maxWaitTimeMillis does not terminate
> -------------------------------------------------------
>
>                 Key: FLINK-20305
>                 URL: https://issues.apache.org/jira/browse/FLINK-20305
>             Project: Flink
>          Issue Type: Bug
>          Components: API / DataStream
>    Affects Versions: 1.12.0
>            Reporter: Till Rohrmann
>            Priority: Minor
>              Labels: auto-deprioritized-major, usability
>             Fix For: 1.15.0, 1.16.0
>
>
> While testing the {{DataStream}} API, I noticed that an iterative job with {{maxWaitTimeMillis}} set, sometimes did not terminate depending on the used parallelism. Since I used a bounded source with few events, it looked a bit as if the iteration tasks couldn't terminate if they didn't receive an event. The corresponding testing job including test data can be found [here|https://github.com/tillrohrmann/flink-streaming-batch-execution/tree/iteration-problem].



--
This message was sent by Atlassian Jira
(v8.20.1#820001)