[
https://issues.apache.org/jira/browse/BEAM-3849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16399983#comment-16399983
]
Tim Robertson commented on BEAM-3849:
-------------------------------------
Setting excplicit defaults rather than infinite (I believe) seems sensible.
For this environment they'd be more like 60-120 seconds though - part of that
is due to the issue that batch sizes can't be tuned either (BEAM-3820) which
means less control for managing load on the target system. Like I wrote on
BEAM-3820 I'd encourage exposing the ability to tune parameters for adapters
that interface with external systems as what you might opt for in one
environment might contradict another. I'm speculating here but I could foresee
a daily bulk job might opt for very conservative values for robustness while
certain streaming jobs might want to fail quickly.
> SolrIO: Expose connection timeout tuning for writes
> ---------------------------------------------------
>
> Key: BEAM-3849
> URL: https://issues.apache.org/jira/browse/BEAM-3849
> Project: Beam
> Issue Type: Improvement
> Components: io-java-solr
> Affects Versions: 2.2.0, 2.3.0
> Reporter: Tim Robertson
> Assignee: Ismaël Mejía
> Priority: Minor
>
> A useful addition would be the ability to tune the socket and conncetion
> timeouts for the underlying solrj client.
> Currently the createHttpClient() uses defaults only.
> This relates to BEAM-3820 and BEAM-3848 which together will help improve
> stability of jobs doing large (billions of docs) loading of SOLR.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
