[
https://issues.apache.org/jira/browse/BEAM-6103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kenneth Knowles updated BEAM-6103:
----------------------------------
Resolution: Fixed
Status: Resolved (was: Resolved)
Hello! Due to a bug in our Jira configuration, this issue had status:Resolved
but resolution:Unresolved.
I am bulk editing these issues to have resolution:Fixed
If a different resolution is appropriate, please change it. To do this, click
the "Resolve" button (you can do this even for closed issues) and set the
Resolution field to the right value.
> Allow setting a HTTP write timeout to requests to BigQuery
> ----------------------------------------------------------
>
> Key: BEAM-6103
> URL: https://issues.apache.org/jira/browse/BEAM-6103
> 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] [https://bugs.java.com/bugdatabase/view_bug.do?bug_id=4031100]
> [2]
> [https://github.com/googleapis/google-http-java-client/releases/tag/v1.27.0]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
