Hello, We have a process which backs up the index (Solr 7.7.2) on a schedule. The way we do it is we first save a commit point on the index and then using Solr's /replication handler, get the list of files in that generation. After the backup completes, we release the commit point (Please note that this is a separate backup process outside of Solr and not the backup command of the /replication handler) The assumption is that while the commit point is saved, no changes happen to the segment files in the saved generation.
Now the issue... The backup process opens the index files in a shared READ mode, preventing writes. This is causing any parallel commits to fail as it seems to be complaining about the index files to be locked by another process(the backup process). Upon debugging, I see that fsync is being called during commit on already existing segment files which is not expected. So, my question is, is there any reason for lucene to call fsync on already existing segment files? The line of code I am referring to is as below: try (final FileChannel file = FileChannel.open(fileToSync, isDir ? StandardOpenOption.READ : StandardOpenOption.WRITE)) in method fsync(Path fileToSync, boolean isDir) of the class file lucene\core\src\java\org\apache\lucene\util\IOUtils.java Thanks, Rahul
