[ https://issues.apache.org/jira/browse/FLINK-19109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17189373#comment-17189373 ]
Roman Khachatryan commented on FLINK-19109: ------------------------------------------- I've published a [PR|https://github.com/apache/flink/pull/13305] to fix the issue in 1.12 and 1.11. For 1.10, the fix would be problematic as it would likely require backporting [changes to ContinuousFileReaderOperator|https://github.com/apache/flink/pull/10435] and [OperatorChain / timers|https://github.com/apache/flink/pull/10151]. Given that there are several workarounds, I think the fix for 1.11 and 1.12 will suffice. > Split Reader eats chained periodic watermarks > --------------------------------------------- > > Key: FLINK-19109 > URL: https://issues.apache.org/jira/browse/FLINK-19109 > Project: Flink > Issue Type: Bug > Components: Runtime / Task > Affects Versions: 1.10.0, 1.10.1, 1.11.0, 1.10.2, 1.11.1 > Reporter: David Anderson > Assignee: Roman Khachatryan > Priority: Critical > Labels: pull-request-available > Fix For: 1.12.0, 1.11.2, 1.10.3 > > > Attempting to generate watermarks chained to the Split Reader / > ContinuousFileReaderOperator, as in > {code:java} > SingleOutputStreamOperator<Event> results = env > .readTextFile(...) > .map(...) > .assignTimestampsAndWatermarks(bounded) > .keyBy(...) > .process(...);{code} > leads to the Watermarks failing to be produced. Breaking the chain, via > {{disableOperatorChaining()}} or a {{rebalance}}, works around the bug. Using > punctuated watermarks also avoids the issue. > Looking at this in the debugger reveals that timer service is being > prematurely quiesced. > In many respects this is FLINK-7666 brought back to life. > The problem is not present in 1.9.3. > There's a minimal reproducible example in > [https://github.com/alpinegizmo/flink-question-001/tree/bug]. -- This message was sent by Atlassian Jira (v8.3.4#803005)