[
https://issues.apache.org/jira/browse/BEAM-6103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17122202#comment-17122202
]
Kenneth Knowles commented on BEAM-6103:
---------------------------------------
This issue is assigned but has not received an update in 30 days so it has been
labeled "stale-assigned". If you are still working on the issue, please give an
update and remove the label. If you are no longer working on the issue, please
unassign so someone else may work on it. In 7 days the issue will be
automatically unassigned.
> 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
> Assignee: Chamikara Madhusanka Jayalath
> Priority: P2
> Labels: stale-assigned
> Time Spent: 1h
> 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)
