[ https://issues.apache.org/jira/browse/SOLR-12550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16870859#comment-16870859 ]
Rahul Goswami commented on SOLR-12550: -------------------------------------- As discussed on the Solr user list, I found this issue on Solr 7.2.1. Providing a patch on 7.2 with GitHub pull request #740 as attached to this Jira with the appropriate description of and solution to the problem. I tried the patch in pull request #417 as submitted by Marc but it won't work, reason being that the builder object which is used to instantiate a ConcurrentUpdateSolrClient itself doesn't contain the timeout values. > 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 > Priority: Major > Time Spent: 20m > 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 (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org