[
https://issues.apache.org/jira/browse/BEAM-10991?focusedWorklogId=493775&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-493775
]
ASF GitHub Bot logged work on BEAM-10991:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 02/Oct/20 02:09
Start Date: 02/Oct/20 02:09
Worklog Time Spent: 10m
Work Description: kennknowles commented on pull request #12993:
URL: https://github.com/apache/beam/pull/12993#issuecomment-702488814
Run Java PreCommit
----------------------------------------------------------------
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: 493775)
Time Spent: 2h (was: 1h 50m)
> Timers don't release watermark holds in dataflow on 2.24
> --------------------------------------------------------
>
> Key: BEAM-10991
> URL: https://issues.apache.org/jira/browse/BEAM-10991
> Project: Beam
> Issue Type: Bug
> Components: runner-dataflow
> Affects Versions: 2.24.0
> Reporter: Steve Niemitz
> Assignee: Kenneth Knowles
> Priority: P1
> Fix For: 2.25.0
>
> Time Spent: 2h
> Remaining Estimate: 0h
>
> We have multiple streaming pipelines (using state + timers) that, after
> upgrading to 2.24, exhibited very strange watermark behavior. The watermark
> on some stateful DoFns would advance to the end of the first window, and then
> get stuck there forever, even preventing the job from draining.
> I was able to track the problem down to
> [https://github.com/apache/beam/commit/88acc5267f759d81e9836a9db17b9e0ee521c785.|https://github.com/apache/beam/commit/88acc5267f759d81e9836a9db17b9e0ee521c785]
> After revering it, the behavior went back to normal. It looks like its
> possible in that commit that watermark holds for some timers aren't being
> cleared.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
