[
https://issues.apache.org/jira/browse/BEAM-14469?focusedWorklogId=770329&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-770329
]
ASF GitHub Bot logged work on BEAM-14469:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 13/May/22 19:16
Start Date: 13/May/22 19:16
Worklog Time Spent: 10m
Work Description: riteshghorse commented on PR #17667:
URL: https://github.com/apache/beam/pull/17667#issuecomment-1126368559
R: @lostluck @youngoli
Issue Time Tracking
-------------------
Worklog Id: (was: 770329)
Time Spent: 3h 10m (was: 3h)
> TestCheckpointing produces too many zero-length restrictions
> ------------------------------------------------------------
>
> Key: BEAM-14469
> URL: https://issues.apache.org/jira/browse/BEAM-14469
> Project: Beam
> Issue Type: Improvement
> Components: sdk-go
> Reporter: Jack McCluskey
> Assignee: Jack McCluskey
> Priority: P2
> Time Spent: 3h 10m
> Remaining Estimate: 0h
>
> The TestCheckpointing integration test produces a large number of zero-length
> restrictions on split, leading to extremely verbose logging and errors when
> run on dataflow/with multiple runners.
>
> This is tied to the offsetrange tracker producing zero-length restrictions on
> TrySplit() calls in edge cases. The unintended usage of the tracker in this
> streaming context creates this issue but did reveal that TrySplit() calls
> were not allowing nil primary returns, which could cause issues moving
> forward.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
