You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Chetan Mehrotra (JIRA)" <ji...@apache.org> on 2015/03/12 10:15:38 UTC

[jira] [Resolved] (OAK-2590) IndexCopier Error occurred while removing deleted files from Local

     [ https://issues.apache.org/jira/browse/OAK-2590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chetan Mehrotra resolved OAK-2590.
----------------------------------
    Resolution: Fixed

As a fix now a info level message would logged. When index gets updated again then next cycle of opening a new directory would again make an attempt to delete such files. Hence such files would never get accumulated and created garbage for long time 

Fixed with http://svn.apache.org/r1666102

> IndexCopier Error occurred while removing deleted files from Local
> ------------------------------------------------------------------
>
>                 Key: OAK-2590
>                 URL: https://issues.apache.org/jira/browse/OAK-2590
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: oak-lucene
>            Reporter: Chetan Mehrotra
>            Assignee: Chetan Mehrotra
>            Priority: Minor
>             Fix For: 1.1.8
>
>
> Under windows, with copy on read mode enabled for the lucene indexes, following WARN logs were seen:
> {code:java}
> 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)
> {code}
> 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



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)