lucene-solr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Luke Forehand (JIRA)" <>
Subject [jira] Commented: (SOLR-1711) Race condition in org/apache/solr/client/solrj/impl/
Date Thu, 25 Mar 2010 19:30:27 GMT


Luke Forehand commented on SOLR-1711:

This is a very serious problem for us.  We have multiple threads adding to the StreamingUpdateSolrServer's
BlockingQueue, and if I bump the thread count high enough (around 10 for my process) I can
reproduce this problem every time.  I'd say this bug is critical enough to warrant a SOLR
bug-fix release.

> Race condition in org/apache/solr/client/solrj/impl/
> ----------------------------------------------------------------------------------
>                 Key: SOLR-1711
>                 URL:
>             Project: Solr
>          Issue Type: Bug
>          Components: clients - java
>    Affects Versions: 1.4, 1.5
>            Reporter: Attila Babo
>            Priority: Critical
>             Fix For: 1.5
>         Attachments: StreamingUpdateSolrServer.patch
>   Original Estimate: 1h
>  Remaining Estimate: 1h
> While inserting a large pile of documents using StreamingUpdateSolrServer there is a
race condition as all Runner instances stop processing while the blocking queue is full. With
a high performance client this could happen quite often, there is no way to recover from it
at the client side.
> In StreamingUpdateSolrServer there is a BlockingQueue called queue to store UpdateRequests,
there are up to threadCount number of workers threads from StreamingUpdateSolrServer.Runner
to read that queue and push requests to a Solr instance. If at one point the BlockingQueue
is empty all workers stop processing it and pushing the collected content to Solr which could
be a time consuming process, sometimes all worker threads are waiting for Solr. If at this
time the client fills the BlockingQueue to full all worker threads will quit without processing
any further and the main thread will block forever.
> There is a simple, well tested patch attached to handle this situation.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message