You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Kenneth Knowles (Jira)" <ji...@apache.org> on 2021/05/15 17:57:02 UTC
[jira] [Updated] (BEAM-10991) Timers don't release watermark holds
in dataflow on 2.24
[ https://issues.apache.org/jira/browse/BEAM-10991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kenneth Knowles updated BEAM-10991:
-----------------------------------
Resolution: Fixed
Status: Resolved (was: Resolved)
Hello! Due to a bug in our Jira configuration, this issue had status:Resolved but resolution:Unresolved.
I am bulk editing these issues to have resolution:Fixed
If a different resolution is appropriate, please change it. To do this, click the "Resolve" button (you can do this even for closed issues) and set the Resolution field to the right value.
> 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: 4h
> 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)