[
https://issues.apache.org/jira/browse/FLINK-20305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-20305:
-----------------------------------
Labels: auto-deprioritized-major usability (was: stale-major usability)
Priority: Minor (was: Major)
This issue was labeled "stale-major" 7 ago and has not received any updates so
it is being deprioritized. If this ticket is actually Major, please raise the
priority and ask a committer to assign you the issue or revive the public
discussion.
> 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.14.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.3.4#803005)
