[jira] [Work logged] (BEAM-9439) KinesisReader does not report correct backlog statistics

["ASF GitHub Bot (Jira)" <ji...@apache.org>]

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

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

                Author: ASF GitHub Bot
            Created on: 06/May/20 11:32
            Start Date: 06/May/20 11:32
    Worklog Time Spent: 10m 
      Work Description: sgraca commented on pull request #11377:
URL: https://github.com/apache/beam/pull/11377#issuecomment-624595925


   Hi @aromanenko-dev Have you been able to make any progress with the review?


----------------------------------------------------------------
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:
users@infra.apache.org


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

    Worklog Id:     (was: 431180)
    Time Spent: 1h  (was: 50m)

> KinesisReader does not report correct backlog statistics 
> ---------------------------------------------------------
>
>                 Key: BEAM-9439
>                 URL: https://issues.apache.org/jira/browse/BEAM-9439
>             Project: Beam
>          Issue Type: Bug
>          Components: io-java-kinesis
>            Reporter: Sam Whittle
>            Assignee: Sebastian Graca
>            Priority: Major
>          Time Spent: 1h
>  Remaining Estimate: 0h
>
> The KinesisReader implementing KinesisIO reports backlog by implementing the
> UnboundedSource.getTotalBacklogBytes()
> method as opposed to the
> UnboundedSource.getSplitBacklogBytes()
> This value is supposed to represent the total backlog across all shards.  This function is implemented by calling SimplifiedKinesisClient.getBacklogBytes with the watermark of the kinesis shards managed within the UnboundedReader instance.  As this watermark may be further ahead than the watermark across all shards, this may miss backlog bytes.
> An additional concern is that the watermark is calculated using a WatermarkPolicy, which means that the watermark may be inconsistent to the kinesis timestamp for querying backlog.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)