[
https://issues.apache.org/jira/browse/FLINK-19907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17224534#comment-17224534
]
Arvid Heise commented on FLINK-19907:
-------------------------------------
[~roman_khachatryan]'s PR fixes the second case while maintaining the first.
The issue is that the watermarks are already emitted from a state that is after
the in-flight data of the output and input.
> Channel state (upstream) can be restored after emission of new elements
> (watermarks)
> ------------------------------------------------------------------------------------
>
> Key: FLINK-19907
> URL: https://issues.apache.org/jira/browse/FLINK-19907
> Project: Flink
> Issue Type: Bug
> Components: Runtime / Network
> Affects Versions: 1.12.0, 1.11.2
> Reporter: Roman Khachatryan
> Assignee: Roman Khachatryan
> Priority: Major
> Fix For: 1.12.0
>
>
> In StreamTask.beforeInvoke:
> 1.
> operatorChain.initializeStateAndOpenOperators(createStreamTaskStateInitializer());
> 2. readRecoveredChannelState();
> But operatorChain.initializeStateAndOpenOperators can emit watermarks (or
> potentially some other stream elements).
> I've encountered this issue while adding an EndOfRecovery marker - in some
> runs of in OverWindowITCase.testRowTimeBoundedPartitionedRangeOver the marker
> was emitted after the watermark.
>
> cc: [~zjwang], [~pnowojski]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
