Hi,

I removed the write.lock file from the index and then restarted the solr 
server, but still the same issue was observed.

Thanks & Regards,
Akreeti Agarwal
(M) +91-8318686601

-----Original Message-----
From: Atita Arora <atitaar...@gmail.com> 
Sent: Wednesday, November 27, 2019 7:21 PM
To: solr-user@lucene.apache.org
Subject: Re: Solr master issue : IndexNotFoundException

It seems to be either the permission problem or maybe because of the write.lock 
file not removed due to process kill.

Did you happen to check this one ?
https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flucene.472066.n3.nabble.com%2FSolrCore-collection1-is-not-available-due-to-init-failure-td4094869.html&amp;data=02%7C01%7CAkreetiA%40hcl.com%7Cdcd1c099bccf4ed715d808d77340ed96%7C189de737c93a4f5a8b686f4ca9941912%7C0%7C0%7C637104595013784239&amp;sdata=SGjPkO92vio%2Ff8c5FqinQleRkz4nfor9fRcC5FEw3Ss%3D&amp;reserved=0

On Wed, Nov 27, 2019 at 2:28 PM Akreeti Agarwal <akree...@hcl.com> wrote:

> Hi All,
>
> I am getting these two errors after restarting my solr master server:
>
> null:org.apache.solr.common.SolrException: SolrCore 'sitecore_web_index'
> is not available due to init failure: Error opening new searcher
>
> Caused by: org.apache.lucene.index.IndexNotFoundException: no 
> segments* file found in 
> LockValidatingDirectoryWrapper(NRTCachingDirectory(MMapDirectory@/solr
> -m/server/solr/sitecore_web_index/data/index
> lockFactory=org.apache.lucene.store.NativeFSLockFactory@5c6c24fd;
> maxCacheMB=48.0 maxMergeSizeMB=4.0))
>
> Please help to resolve this.
>
> Thanks & Regards,
> Akreeti Agarwal
> (M) +91-8318686601
>
> ::DISCLAIMER::
> ________________________________
> The contents of this e-mail and any attachment(s) are confidential and 
> intended for the named recipient(s) only. E-mail transmission is not 
> guaranteed to be secure or error-free as information could be 
> intercepted, corrupted, lost, destroyed, arrive late or incomplete, or 
> may contain viruses in transmission. The e mail and its contents (with 
> or without referred errors) shall therefore not attach any liability 
> on the originator or HCL or its affiliates. Views or opinions, if any, 
> presented in this email are solely those of the author and may not 
> necessarily reflect the views or opinions of HCL or its affiliates. 
> Any form of reproduction, dissemination, copying, disclosure, 
> modification, distribution and / or publication of this message 
> without the prior written consent of authorized representative of HCL 
> is strictly prohibited. If you have received this email in error 
> please delete it and notify the sender immediately. Before opening any 
> email and/or attachments, please check them for viruses and other defects.
> ________________________________
>

Reply via email to