You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2020/09/02 16:38:00 UTC

[jira] [Work logged] (BEAM-10808) StreamingDataflowWorker streaming rpcs due not always observe stream failures, until timeout

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

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

                Author: ASF GitHub Bot
            Created on: 02/Sep/20 16:37
            Start Date: 02/Sep/20 16:37
    Worklog Time Spent: 10m 
      Work Description: reuvenlax merged pull request #12688:
URL: https://github.com/apache/beam/pull/12688


   


----------------------------------------------------------------
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: 477969)
    Time Spent: 50m  (was: 40m)

> StreamingDataflowWorker streaming rpcs due not always observe stream failures, until timeout
> --------------------------------------------------------------------------------------------
>
>                 Key: BEAM-10808
>                 URL: https://issues.apache.org/jira/browse/BEAM-10808
>             Project: Beam
>          Issue Type: Bug
>          Components: runner-dataflow
>            Reporter: Sam Whittle
>            Assignee: Sam Whittle
>            Priority: P2
>          Time Spent: 50m
>  Remaining Estimate: 0h
>
> The StreamingDataflow worker communicates to Streaming Engine with grpc streaming rpcs. Occasionaly with service failures, the error is not observed by the streaming rpc until the deadline is exceeded.  As the deadline is multiple minutes, this adds unnecessary latency to pipelines that are otherwise keeping up with seconds delay.
> Testing has shown that grpc channel health checks are not sufficient but that application level health checks ensure that streaming rpc health issues are detected earlier than the stream timeout.



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