beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Work logged] (BEAM-3848) SolrIO: Improve retrying mechanism in client writes
Date Mon, 26 Mar 2018 15:27:00 GMT


ASF GitHub Bot logged work on BEAM-3848:

                Author: ASF GitHub Bot
            Created on: 26/Mar/18 15:26
            Start Date: 26/Mar/18 15:26
    Worklog Time Spent: 10m 
      Work Description: iemejia commented on a change in pull request #4905: [BEAM-3848] Enables
ability to retry Solr writes on error (SolrIO)

 File path: sdks/java/io/solr/src/main/java/org/apache/beam/sdk/io/solr/
 @@ -661,25 +746,51 @@ public void processElement(ProcessContext context) throws Exception
         SolrInputDocument document = context.element();
         if (batch.size() >= spec.getMaxBatchSize()) {
-          flushBatch();
+          flushBatch(solrClient, batch);
 Review comment:
   I suppose the new solrClient parameter in this method is to be able to test it, if this
is the case I would prefer that we remove it from there and expose it as a package private
method in the WriteFn class with the `@VisibleForTesting` annotation. Hope it does not make
the mocking of the tests too complicated, but it is just to let the internal state hidden.

This is an automated message from the Apache Git Service.
To respond to the message, please log on 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: 84392)

> SolrIO: Improve retrying mechanism in client writes
> ---------------------------------------------------
>                 Key: BEAM-3848
>                 URL:
>             Project: Beam
>          Issue Type: Improvement
>          Components: io-java-solr
>    Affects Versions: 2.2.0, 2.3.0
>            Reporter: Tim Robertson
>            Assignee: Tim Robertson
>            Priority: Minor
>          Time Spent: 1.5h
>  Remaining Estimate: 0h
> 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

This message was sent by Atlassian JIRA

View raw message