Description
Under windows, with copy on read mode enabled for the lucene indexes, following WARN logs were seen:
03.02.2015 17:40:58.952 *WARN* [pool-5-thread-2] org.apache.jackrabbit.oak.plugins.index.lucene.IndexCopier Error occurred while removing deleted files from Local MMapDirectory@D:\repository\index\e5a943cdec3000bd8ce54924fd2070ab5d1d35b9ecf530963a3583d43bf28293\1 lockFactory=NativeFSLockFactory@D:\repository\index\e5a943cdec3000bd8ce54924fd2070ab5d1d35b9ecf530963a3583d43bf28293\1, Remote OakDirectory@232fe713 lockFactory=org.apache.lucene.store.NoLockFactory@696097fc java.io.IOException: Cannot delete D:\repository\index\e5a943cdec3000bd8ce54924fd2070ab5d1d35b9ecf530963a3583d43bf28293\1\_wq4.cfs at org.apache.lucene.store.FSDirectory.deleteFile(FSDirectory.java:273) at org.apache.jackrabbit.oak.plugins.index.lucene.IndexCopier$CopyOnReadDirectory.removeDeletedFiles(IndexCopier.java:274) at org.apache.jackrabbit.oak.plugins.index.lucene.IndexCopier$CopyOnReadDirectory.access$1000(IndexCopier.java:113) at org.apache.jackrabbit.oak.plugins.index.lucene.IndexCopier$CopyOnReadDirectory$2.run(IndexCopier.java:247) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source)
As the files are memory mapped and the handle is yet not GC its possible that windows would not allow to delete such file. In such a case the log message should be improved and possibly have a way where attempt is made to delete such files later
Attachments
Issue Links
- relates to
-
OAK-2709 Misleading log message from IndexCopier
- Closed