lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shawn Heisey (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SOLR-12550) ConcurrentUpdateSolrClient doesn't respect timeouts for commits and optimize
Date Thu, 12 Jul 2018 23:52:00 GMT

    [ https://issues.apache.org/jira/browse/SOLR-12550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16542336#comment-16542336
] 

Shawn Heisey commented on SOLR-12550:
-------------------------------------

Without seeing exactly what code you've written and what configuration options you have, it
is difficult to determine whether this is a bug or a usage problem.  Can you provide those
details?  We will also need to know the Solr version, and may need logs from the server. 
Without the Solr version, we can't even start looking at source code.

This should have been brought up on the mailing list or IRC channel before opening an issue
in Jira.  If it turns out that it's actually a bug, then Jira is appropriate.

Note:  ConcurrentUpdateSolrClient is not a good choice for production index updating.  It
swallows all indexing errors, so your Solr server could be completely down and all document
updates that you send will appear to your program to have succeeded.


> 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-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message