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 > lockFactory=org.apache.lucene.store.NativeFSLockFactory@4ed4f74c; > maxCacheMB=48.0 maxMergeSizeMB=4.0)): files: [_312.fdx, _30g.nvd, > _2ug_18.liv, _30f_Lucene50_0.doc, _2za.si, _310.si, _30l_Lucene50_0.pos, > _30k_Lucene50_0.tip]
It's saying that it can't find one or more files in the index, without which it cannot open the index. If those eight files listed in the error message are the only files found in that directory, then that index is *extremely* incomplete. It is missing a lot more than the segments* file(s) that the message indicates. In order to get up and running again, you can simply delete all data from the core on that slave and restart it. If the slave config is correct, then on restart, the entire index should be copied from the master server. Just delete or rename the following directory on the slave. You're probably going to need to stop the Solr process before it will let you do so: D:\Solr8.2\solr-5.5.4\solr-5.5.4\server\solr\collection_web_index\data Make sure that you have enough disk space available to hold the index at least twice, and that the user executing the Solr service has write permission. As for why this happened, that information is not available in what you have shared. Are there any ERROR or WARN messages in the logfile before that message? If so, those may provide hints about what went wrong. Note that I am not talking about the logging tab in the admin UI. You will need to actually go find the logs directory and examine the logfiles. Thanks, Shawn
