On 2/28/2023 2:20 AM, Paul Ryder wrote:
All,

I see warnings in the Solr master replication like this

2023-02-24 18:10:40.964 WARN  (qtp156856360-13173) [   x:Fred_apis_responses_index] 
o.a.s.h.ReplicationHandler Exception while writing response for params: 
generation=394103&qt=/replication&file=segments_8g3b&checksum=true&compression=true&wt=filestream&command=filecontent
 => java.nio.file.NoSuchFileException: 
E:\Solr8.1.1\Fred_apis_responses_index\data\restore.20221207055103765\segments_8g3b
                 at sun.nio.fs.WindowsException.translateToIOException(Unknown 
Source)

Not sure why a file that is expected to be there isn't there.

And warnings/errors on Slave servers such as

File _exa0_Lucene50_0.tim did not match. expected checksum is 1661977412 and 
actual is checksum 116298600. expected length is 4648 and actual length is 4145

This sounds like a file got corrupted.  Something changed it.

Error removing directory 
E:\Solr8.1.1\Fred_documentsearch_index\data\index.20230228073716425 before core 
close:java.io.IOException: Unable to delete file: 
E:\Solr8.1.1\Fred_documentsearch_index\data\index.20230228073716425\_ex9o.cfs

Solr 8.1.1 on Java 8 - Windows

Windows can't delete a file that something has open in ANY mode. Linux and other similar operating systems have no trouble deleting open files.  Software like Solr just works better on most open source operating systems than on Windows.

The question comes down to why that file is open when Lucene (the central Search API used by Solr) tries to delete it.  This can be caused by antivirus software, backup software, or several other possibilities.  I can see antivirus software causing all of the problems you have described.  You should exclude the place Solr stores its indexes from scanning by antivirus software.

In addition to problems that running on Windows can cause, there is the fact that Solr 8.1.1 is nearly four years old and is basically unsupported.  Any problems you find would need to be demonstrated as happening in the latest Solr version, and due to a bug in Solr, not some aspect of the environment.

Thanks,
Shawn

Reply via email to