You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@beam.apache.org by "Tim Robertson (JIRA)" <ji...@apache.org> on 2018/03/16 15:00:00 UTC

[jira] [Commented] (BEAM-3848) SolrIO: Improve retrying mechanism in client writes

    [ https://issues.apache.org/jira/browse/BEAM-3848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16402003#comment-16402003 ] 

Tim Robertson commented on BEAM-3848:
-------------------------------------

I am going to work on this. 

There have been discussions recently with [~kirpichov] (BEAM-3820) on whether tuning params should be surfaced. Should this be an option or always on and fully hidden? 

I'll tackle BEAM-3026 which is the sister issue for ElasticSearchIO in the same manner. In that issue it was proposed surfacing it as optional.

> SolrIO: Improve retrying mechanism in client writes
> ---------------------------------------------------
>
>                 Key: BEAM-3848
>                 URL: https://issues.apache.org/jira/browse/BEAM-3848
>             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 busy SOLR server is prone to return RemoteSOLRException on writing which currently fails a complete task (e.g. a partition of a spark RDD being written to SOLR).
> A good addition would be the ability to provide a retrying mechanism for the batch in flight, rather than failing fast, which will most likely trigger a much larger retry of more writes.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)