Hi,
The index is the fresh one (older index deleted) and there is no soft
commit on them.
There are other logs available a part of which is as follows:
Apr 11, 2014 9:34:49 AM org.apache.solr.common.SolrException log
SEVERE: null:org.apache.solr.common.SolrException: Unable to create core:
On 4/14/2014 10:25 PM, Modassar Ather wrote:
Caused by: org.apache.lucene.store.LockObtainFailedException: Lock obtain
timed out: NativeFSLock@path/data/index/write.lock:
java.io.FileNotFoundException: path/data/index/write.lock (Permission
denied)
This sounds like the user (the one that's
Thanks Shawn for your suggestion.
Earlier the write permission was set only on the *data *directory. Per your
suggestion after providing write access to
*data/index* folder and all the files under it the core gets loaded.
Regards,
Modassar
On Tue, Apr 15, 2014 at 10:12 AM, Shawn Heisey
Hi,
I indexed few documents under a core of Solr 4.6.1 instance deployed on
Tomcat and copied the same index to other Solr instance with a core having
same configurations.
Before copying the index, source Solr instance was stopped. But when I
start the other instance with the copied index it
On 4/13/2014 10:05 PM, Modassar Ather wrote:
I indexed few documents under a core of Solr 4.6.1 instance deployed on
Tomcat and copied the same index to other Solr instance with a core having
same configurations.
Before copying the index, source Solr instance was stopped. But when I
start the
