[
https://issues.apache.org/jira/browse/SOLR-12550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17040938#comment-17040938
]
ASF subversion and git services commented on SOLR-12550:
--------------------------------------------------------
Commit 8eb6b03d51c005448f0f046a20eed07039e14606 in lucene-solr's branch
refs/heads/branch_8x from Marc A. Morissette
[ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=8eb6b03 ]
SOLR-12550: ConcurrentUpdateSolrClient doesn't respect timeouts for commits and
optimize (#417)
ConcurrentUpdateSolrClient now propagates its connection and read timeouts to
the private HttpSolrClient used to commit and optimize.
(cherry picked from commit 051133c13f982e72aabf914350c65e3dd8aa961d)
> ConcurrentUpdateSolrClient doesn't respect timeouts for commits and optimize
> ----------------------------------------------------------------------------
>
> Key: SOLR-12550
> URL: https://issues.apache.org/jira/browse/SOLR-12550
> Project: Solr
> Issue Type: Bug
> Reporter: Marc Morissette
> Assignee: Shalin Shekhar Mangar
> Priority: Major
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> We're in a situation where we need to optimize some of our collections. These
> optimizations are done with waitSearcher=true as a simple throttling
> mechanism to prevent too many collections from being optimized at once.
> We're seeing these optimize commands return without error after 10 minutes
> but well before the end of the operation. Our Solr logs show errors with
> socketTimeout stack traces. Setting distribUpdateSoTimeout to a higher value
> has no effect.
> See the links section for my patch.
> It turns out that ConcurrentUpdateSolrClient delegates commit and optimize
> commands to a private HttpSolrClient but fails to pass along its builder's
> timeouts to that client.
> A patch is attached in the links section.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
