Mailing-List: contact dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@lucene.apache.org
Date: Wed, 3 Aug 2011 14:08:27 +0000 (UTC)
From: "Yonik Seeley (JIRA)" <jira@apache.org>
To: dev@lucene.apache.org
Message-ID: 
 <1358698451.4725.1312380507385.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <602418720.4676.1312378713396.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (SOLR-2694) LogUpdateProcessor not thread safe
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/SOLR-2694?page=3Dcom.atlassian.=
jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D13078=
758#comment-13078758 ]=20

Yonik Seeley commented on SOLR-2694:
------------------------------------

A new update processor is built for every request, and hence they are not t=
hread safe by design.
How is this log processor getting shared between multiple threads?

> 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=C3=B8ydahl
>
> Using the LogUpdateProcessor while feeding in multiple parallell threads =
does not work, as LogUpdateProcessor is not threadsafe.

--
This message is automatically generated by JIRA.
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