On 5/8/2018 4:32 AM, Aji Viswanadhan wrote:
Is this issue happened due to the size of the index? or any recommendations
to not happen in future. Please let me know.
I have no idea why it happened. Running out of disk space could cause
any number of problems. Program operation becomes unpredi
Hi Shawn ,
Thanks for the info!!
As I mentioned master index was fine, only for one of the collection in
salve index was corrupted. Yes, we fixed the issue by removing corrupted
index and replicated again.
The error message shared we have received from Admin UI of Solr. Replication
strategy see
On 5/4/2018 4:29 AM, Aji Viswanadhan wrote:
> Caused by: org.apache.lucene.index.IndexNotFoundException: no segments* file
> found in
> LockValidatingDirectoryWrapper(NRTCachingDirectory(MMapDirectory@D:\Solr8.2\solr-5.5.4\solr-5.5.4\server\solr\collection_web_index\data\index.20180428184955635
> l
Hi Team,
We have the Solr setup in our project and it has SOLR Master and SOLR
Slaves.
The setup is working fine and the replication also happens properly. This
week we had the issue as one slave was not able to initialize one collection
and it seems index was corrupted in the slave.
Here is the
