[ 
https://issues.apache.org/jira/browse/FLINK-19109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17191651#comment-17191651
 ] 

Piotr Nowojski commented on FLINK-19109:
----------------------------------------

[~alpinegizmo] those two PRs that the fix depends on are quite big changes 
(+2000 lines of code), with some follow up bug fixes. Back porting them could 
mean destabilising the 1.10.x release branch, especially given that our release 
testing for minor changes is not that good. Furthermore, they are changing 
behaviour of the system, for example the [ContinuousFileReaderOperator 
changes|https://github.com/apache/flink/pull/10435] will be affecting 
performance (hopefully improving), while the other one FLINK-14228 is changing 
semantic of timers during shutdown.

Is there other way to fix the problem [~roman_khachatryan]?

> 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: Blocker
>              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)

Reply via email to