lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ethan Tao (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SOLR-2694) LogUpdateProcessor not thread safe
Date Tue, 22 May 2012 07:11:41 GMT

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

Ethan Tao commented on SOLR-2694:
---------------------------------

Hoss: The issue described in Solr-2804 also helps to some extend. 
We are building document indexing pipeline. The update chain we defined is enforced with singleton,
thus the LogUpdateProcessor is shared among concurrent threads. We didn't realize the class
is thread unsafe till now. 

We'll try the workaround to reduce its log level below INFO and see if it's acceptable. We'll
create a new bug if necessary.
Thanks a lot.

-Ethan
                
> LogUpdateProcessor not thread safe
> ----------------------------------
>
>                 Key: SOLR-2694
>                 URL: https://issues.apache.org/jira/browse/SOLR-2694
>             Project: Solr
>          Issue Type: Bug
>          Components: update
>    Affects Versions: 1.4.1, 3.1, 3.2, 3.3, 4.0
>            Reporter: Jan H√łydahl
>
> Using the LogUpdateProcessor while feeding in multiple parallell threads does not work,
as LogUpdateProcessor is not threadsafe.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message