[SOLR-12550] ConcurrentUpdateSolrClient doesn't respect timeouts for commits and optimize

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 8.5, 9.0
• Component/s: SolrJ
• Assignee: Shalin Shekhar Mangar
• Reporter: Marc Morissette
• Created: 12/Jul/18 21:22
• Updated: 08/Dec/21 13:24
• Resolved: 20/Feb/20 12:57

Description

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.

Issue Links

• is related to: SOLR-13457 Managing Timeout values in Solr
• relates to: SOLR-12314 ConcurrentUpdateSolrClient doesn't respect the timeout's defined in the solr.xml file
• relates to: SOLR-13605 HttpSolrClient.Builder.withHttpClient() is useless for the purpose of setting client scoped so/connect timeouts
• links to: GitHub Pull Request #417
• links to: GitHub Pull Request #417
• links to: GitHub Pull Request #740