[
https://issues.apache.org/jira/browse/SOLR-12550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16542261#comment-16542261
]
Marc Morissette commented on SOLR-12550:
----------------------------------------
By the way, I have not investigated why the optimize() command returns without
an error despite the fact that it did not complete normally.
> 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
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Marc Morissette
> Priority: Major
> Time Spent: 10m
> 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.
> 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.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
