Lucene index Lock

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Lucene index Lock

Jacques Le Roux
Administrator
Hi,

Should we worry about this message I found in error.log?

2016-06-07 10:35:23,327 |xer_default_products |DocumentIndexer               |E| Could not obtain Lock on lucene index Lock held by this virtual
machine: C:\projectASF-Mars\ofbiz\runtime\indexes\products\write.lock

I tested indexing contents and products works w/o pb.

Jacques



Reply | Threaded
Open this post in threaded view
|

Re: Lucene index Lock

Jacopo Cappellato-5
We should not worry (because the "lucene" component is just an experimental
one) but let's keep an eye on it: it is caused when two threads are trying
to update documents in the Lucene index; it may happen when two events
modify data that trigger the execution of the document update.
We could consider to enhance the DocumentIndexer to properly manage these
scenarios.

Jacopo



On Tue, Jun 7, 2016 at 10:55 AM, Jacques Le Roux <
[hidden email]> wrote:

> Hi,
>
> Should we worry about this message I found in error.log?
>
> 2016-06-07 10:35:23,327 |xer_default_products |DocumentIndexer
>    |E| Could not obtain Lock on lucene index Lock held by this virtual
> machine: C:\projectASF-Mars\ofbiz\runtime\indexes\products\write.lock
>
> I tested indexing contents and products works w/o pb.
>
> Jacques
>
>
>
>
Reply | Threaded
Open this post in threaded view
|

Re: Lucene index Lock

Jacques Le Roux
Administrator
Thanks Jacopo,

I'll create a Jira using your answer as description

Jacques


Le 08/06/2016 à 15:08, Jacopo Cappellato a écrit :

> We should not worry (because the "lucene" component is just an experimental
> one) but let's keep an eye on it: it is caused when two threads are trying
> to update documents in the Lucene index; it may happen when two events
> modify data that trigger the execution of the document update.
> We could consider to enhance the DocumentIndexer to properly manage these
> scenarios.
>
> Jacopo
>
>
>
> On Tue, Jun 7, 2016 at 10:55 AM, Jacques Le Roux <
> [hidden email]> wrote:
>
>> Hi,
>>
>> Should we worry about this message I found in error.log?
>>
>> 2016-06-07 10:35:23,327 |xer_default_products |DocumentIndexer
>>     |E| Could not obtain Lock on lucene index Lock held by this virtual
>> machine: C:\projectASF-Mars\ofbiz\runtime\indexes\products\write.lock
>>
>> I tested indexing contents and products works w/o pb.
>>
>> Jacques
>>
>>
>>
>>