[jira] [Commented] (OFBIZ-7265) Could not obtain Lock on lucene index Lock

[Nicolas Malin (Jira)]

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

Amardeep Singh Jhajj commented on OFBIZ-7265:
---------------------------------------------

Hi [~jacques.le.roux],

I am able to reproduce this on my dev machine. Here is the steps to regenerate it:

1. Go to https://localhost:8443/content/control/AdminIndex
2. Click on Index Products button.

As per my analysis, the reason of error is write lock on lucene indexes (created by lucene indexing process in lucene component) by Solr. Have a look on specialpurpose/solr/home/solrdefault/conf/solrconfig.xml line:

{code}
  <dataDir>${solr.data.dir:runtime/indexes}</dataDir>
{code}

Should point to:

{code}
  <dataDir>${solr.data.dir:specialpurpose/solr/home/solrdefault/runtime/indexes/}</dataDir>
{code}

Solr currently pointing to lucene indexes and creating a lock on it. We can't index products anymore using lucene indexing as it has lock from Solr.

So currently all the search results we can see on Solr Search

{code}
https://localhost:8443/solr/#/solrdefault/query 
{code}

is lucene indexed results.

We have not created any indexes using Solr itself. Thanks

> Could not obtain Lock on lucene index Lock
> ------------------------------------------
>
>                 Key: OFBIZ-7265
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-7265
>             Project: OFBiz
>          Issue Type: Bug
>          Components: specialpurpose/lucene
>    Affects Versions: Trunk
>            Reporter: Jacques Le Roux
>            Priority: Minor
>
> I found this message in error.log
> |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
> Here is Jacopo's answer:
> bq. 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.

--
This message was sent by Atlassian JIRA
(v6.3.4#6332)