[
https://issues.apache.org/jira/browse/BEAM-10691?focusedWorklogId=470137&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-470137
]
ASF GitHub Bot logged work on BEAM-10691:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 13/Aug/20 08:20
Start Date: 13/Aug/20 08:20
Worklog Time Spent: 10m
Work Description: mxm commented on pull request #12551:
URL: https://github.com/apache/beam/pull/12551#issuecomment-673336167
It's likely caused by using the output timestamp feature in the wrong way.
If you use a fire timestamp too far in the future, it can easily stall the
entire pipeline. It's a pretty dangerous feature which should be avoided if
possible.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 470137)
Time Spent: 1h 50m (was: 1h 40m)
> FlinkRunner: pipeline might get stuck due to timer watermark hold not being
> released
> ------------------------------------------------------------------------------------
>
> Key: BEAM-10691
> URL: https://issues.apache.org/jira/browse/BEAM-10691
> Project: Beam
> Issue Type: Bug
> Components: runner-flink
> Affects Versions: 2.23.0, 2.24.0
> Reporter: Jan Lukavský
> Assignee: Jan Lukavský
> Priority: P1
> Time Spent: 1h 50m
> Remaining Estimate: 0h
>
> Pipeline might stop progressing watermark in certain cases due to timer
> output timestamp not being released from
> FlinkTimerInternals#outputTimestampQueue. The pipeline has to be restarted
> from checkpoint to reload the cache and free watermark hold.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
