This can mean multiple things:
1. You had killed a solr process earlier which left the lock file in place
2. You have more than one Solr core pointing to the same data directory
3. A solr process is already running and you are trying to start
another one with the same config.

On Fri, Jul 5, 2013 at 2:34 PM, Cool Techi <cooltec...@outlook.com> wrote:
> We have set up solr 4.3 with master/setup and are facing a couple of issues,
>
> Index locking, the index on slave hangs at time and when we restart the core 
> the core get's locked up. I have checked the logs and there are no OOM error 
> or anything else other than the error given below,Caused by: 
> org.apache.solr.common.SolrException: Index locked for write for core XXX
>     at org.apache.solr.core.SolrCore.<init>(SolrCore.java:821)
>     at org.apache.solr.core.SolrCore.<init>(SolrCore.java:618)
>     at 
> org.apache.solr.core.CoreContainer.createFromLocal(CoreContainer.java:949)
>     at org.apache.solr.core.CoreContainer.create(CoreContainer.java:984)
>     at org.apache.solr.core.CoreContainer$2.call(CoreContainer.java:597)
>     at org.apache.solr.core.CoreContainer$2.call(CoreContainer.java:592)
>     at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
>     at java.util.concurrent.FutureTask.run(FutureTask.java:138)
>     at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439)
>     at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
>     at java.util.concurrent.FutureTask.run(FutureTask.java:138)
>     at 
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
>     at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
>     ... 1 more
> Caused by: org.apache.lucene.store.LockObtainFailedException: Index locked 
> for write for core XX        at 
> org.apache.solr.core.SolrCore.initIndex(SolrCore.java:484)
>     at org.apache.solr.core.SolrCore.<init>(SolrCore.java:745)
>     ... 13 moreWhen we fire backup on Slave, the whole core hangs after a 
> while and also replication stops. This was not happening with our earlier 
> setup of solr3.6
>
>
>
> Regards,
> Ayush
>
>
>
>
>
>
>
>
>
>
>
>
>
>



-- 
Regards,
Shalin Shekhar Mangar.

Reply via email to