beam-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (Jira)" <>
Subject [jira] [Work logged] (BEAM-6103) Allow setting a HTTP write timeout to requests to BigQuery
Date Fri, 25 Sep 2020 13:35:00 GMT


ASF GitHub Bot logged work on BEAM-6103:

                Author: ASF GitHub Bot
            Created on: 25/Sep/20 13:34
            Start Date: 25/Sep/20 13:34
    Worklog Time Spent: 10m 
      Work Description: udim merged pull request #12893:


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:

Issue Time Tracking

    Worklog Id:     (was: 491008)
    Time Spent: 3h 10m  (was: 3h)

> Allow setting a HTTP write timeout to requests to BigQuery
> ----------------------------------------------------------
>                 Key: BEAM-6103
>                 URL:
>             Project: Beam
>          Issue Type: Bug
>          Components: io-java-gcp
>    Affects Versions: Not applicable
>            Reporter: Chamikara Madhusanka Jayalath
>            Priority: P3
>          Time Spent: 3h 10m
>  Remaining Estimate: 0h
> Several users have reported that very occasionally some of the streaming insert requests
to BigQuery are getting stuck. 
> This can be mitigated by setting a write timeout for sockets and allowing runners to
retry. But Java does not support setting write timeouts for non-NIO sockets [1] and this
bug affects Google HTTP client library used by GCP IO.
> Google HTTP library was recently updated to support write timeouts [2]. So we can update
BigQueryIO to utilize this feature and allow setting a write timeout. Setting write timeout
results in more threads being created. So this path can be slightly expensive and hence should
not be made the default path.
> [1] []
> [2] []

This message was sent by Atlassian Jira

View raw message