[ 
https://issues.apache.org/jira/browse/BEAM-14469?focusedWorklogId=770340&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-770340
 ]

ASF GitHub Bot logged work on BEAM-14469:
-----------------------------------------

                Author: ASF GitHub Bot
            Created on: 13/May/22 19:38
            Start Date: 13/May/22 19:38
    Worklog Time Spent: 10m 
      Work Description: github-actions[bot] commented on PR #17667:
URL: https://github.com/apache/beam/pull/17667#issuecomment-1126389008

   Assigning reviewers. If you would like to opt out of this review, comment 
`assign to next reviewer`:
   
   R: @riteshghorse for label go.
   
   Available commands:
   - `stop reviewer notifications` - opt out of the automated review tooling
   - `remind me after tests pass` - tag the comment author after tests pass
   - `waiting on author` - shift the attention set back to the author (any 
comment or push by the author will return the attention set to the reviewers)
   
   The PR bot will only process comments in the main thread (not review 
comments).




Issue Time Tracking
-------------------

    Worklog Id:     (was: 770340)
    Time Spent: 3.5h  (was: 3h 20m)

> 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: 3.5h
>  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)

Reply via email to