lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Naresh Kumar Geepalem (JIRA)" <>
Subject [jira] [Created] (SOLR-9892) Core is locked
Date Mon, 26 Dec 2016 15:06:58 GMT
Naresh Kumar Geepalem created SOLR-9892:

             Summary: Core is locked
                 Key: SOLR-9892
             Project: Solr
          Issue Type: Bug
      Security Level: Public (Default Security Level. Issues are Public)
         Environment: UAT
            Reporter: Naresh Kumar Geepalem

Hi Team,

We have setup of one master and two slaves. One master and one slave one server (same JVM)
and another slave in different server. This setup is working fine from past 6 months including
production environment.

Now, we are facing below issue in master solr.

org.apache.solr.common.SolrException:org.apache.solr.common.SolrException: Index dir 'D:\inetpub\wwwroot\CMS-Solr\Solr\solr-5.4.1\server\solr\sitecore_marketing_asset_index_master\data\index/'
of core 'sitecore_marketing_asset_index_master' is already locked. The most likely cause is
another Solr server (or another solr core in this server) also configured to use this directory;
other possible causes may be specific to lockType: native                                sitecore_web_index:
org.apache.solr.common.SolrException:org.apache.solr.common.SolrException: Index dir 'D:\inetpub\wwwroot\CMS-Solr\Solr\

We have stopped both slaves and restarted master. Still same issue is coming. We have deleted
write.lock file from all cores under data/index.
Then "site cant be reached" message is showing when access solr url.

Can some one please provide information on how to fix this as we are struck with this issue
during UAT?

G. Naresh Kumar

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message