Index segment lost after consistency check
------------------------------------------

                 Key: JCR-1058
                 URL: https://issues.apache.org/jira/browse/JCR-1058
             Project: Jackrabbit
          Issue Type: Bug
          Components: indexing
    Affects Versions: 1.3
            Reporter: Christoph Kiehl
            Priority: Critical


On one of our server it seems like a whole index segment got lost because all 
nodes that were added just before the crash where not in the index anymore an 
we got this in out log file:

[2007-07-06 10:52:08,067, INFO ] {} 
he.jackrabbit.core.query.lucene.Recovery:86: Redo changes applied.
[2007-07-06 10:52:08,073, INFO ] {} 
jackrabbit.core.query.lucene.SearchIndex:298: Running consistency check...
[2007-07-06 10:52:09,495, INFO ] {} 
jackrabbit.core.query.lucene.IndexMerger:268: merged 3710 documents in 1384 ms 
into _2j2f.
[2007-07-06 10:59:30,600, INFO ] {} 
abbit.core.query.lucene.ConsistencyCheck:160: progress: 10%
[2007-07-06 11:06:45,543, INFO ] {} 
abbit.core.query.lucene.ConsistencyCheck:160: progress: 20%
[2007-07-06 11:13:42,292, INFO ] {} 
abbit.core.query.lucene.ConsistencyCheck:160: progress: 30%
[2007-07-06 11:20:46,071, INFO ] {} 
abbit.core.query.lucene.ConsistencyCheck:160: progress: 40%
[2007-07-06 11:27:54,927, INFO ] {} 
abbit.core.query.lucene.ConsistencyCheck:160: progress: 50%
[2007-07-06 11:28:00,446, INFO ] {} 
abbit.core.query.lucene.ConsistencyCheck:190: progress: 60%
[2007-07-06 11:28:05,898, INFO ] {} 
abbit.core.query.lucene.ConsistencyCheck:190: progress: 70%
[2007-07-06 11:28:11,091, INFO ] {} 
abbit.core.query.lucene.ConsistencyCheck:190: progress: 80%
[2007-07-06 11:28:16,030, INFO ] {} 
abbit.core.query.lucene.ConsistencyCheck:190: progress: 90%
[2007-07-06 11:28:21,030, INFO ] {} 
abbit.core.query.lucene.ConsistencyCheck:190: progress: 100%
[2007-07-06 11:28:21,040, INFO ] {} 
abbit.core.query.lucene.ConsistencyCheck:285: Reparing missing node /
[2007-07-06 11:28:21,048, INFO ] {} 
abbit.core.query.lucene.ConsistencyCheck:132: Repaired 1 errors.
[2007-07-06 11:28:21,050, INFO ] {} 
jackrabbit.core.query.lucene.SearchIndex:318: Index initialized: 
/foo/bar/repository/repository/index
[2007-07-06 11:28:21,072, INFO ] {} 
jackrabbit.core.fs.local.LocalFileSystem:166: LocalFileSystem initialized at 
path /foo/bar/repository/workspaces/default/index
[2007-07-06 11:28:21,149, INFO ] {} 
he.jackrabbit.core.query.lucene.Recovery:83: Found uncommitted redo log. 
Applying changes now...
[2007-07-06 11:28:21,151, WARN ] {} 
rabbit.core.query.lucene.PersistentIndex:86: Removing write lock on search 
index.
[2007-07-06 11:28:21,280, INFO ] {} 
he.jackrabbit.core.query.lucene.Recovery:86: Redo changes applied.
[2007-07-06 11:28:21,282, INFO ] {} 
jackrabbit.core.query.lucene.SearchIndex:298: Running consistency check...
[2007-07-06 11:28:21,475, WARN ] {} 
jackrabbit.core.query.lucene.SearchIndex:315: Failed to run consistency check 
on index: java.io.IOException: No such file or directory
[2007-07-06 11:28:21,477, INFO ] {} 
jackrabbit.core.query.lucene.SearchIndex:318: Index initialized: 
/foo/bar/repository/workspaces/default/index
[2007-07-06 11:28:21,478, INFO ] {} 
rg.apache.jackrabbit.core.RepositoryImpl:329: Repository started
[2007-07-06 11:28:23,241, INFO ] {} 
jackrabbit.core.query.lucene.IndexMerger:268: merged 12416 documents in 1919 ms 
into _4n3i.
[2007-07-06 11:28:23,279, ERROR] {} 
jackrabbit.core.query.lucene.IndexMerger:302: Error while merging indexes: 
java.io.IOException: No such file or directory 

A bit later while trying to commit a transaction the following exception was 
logged:

[2007-07-06 11:29:09,797, ERROR] {} 
org.apache.jackrabbit.core.SearchManager:427: Error indexing node.
java.io.IOException: No such file or directory
        at java.io.UnixFileSystem.createFileExclusively(Native Method)
        at java.io.File.createNewFile(File.java:883)
        at 
org.apache.jackrabbit.core.query.lucene.FSDirectory$1.obtain(FSDirectory.java:119)
        at org.apache.lucene.store.Lock.obtain(Lock.java:51)
        at 
org.apache.lucene.index.IndexReader.aquireWriteLock(IndexReader.java:489)
        at 
org.apache.lucene.index.IndexReader.deleteDocument(IndexReader.java:514)
        at 
org.apache.lucene.index.FilterIndexReader.doDelete(FilterIndexReader.java:132)
        at 
org.apache.lucene.index.IndexReader.deleteDocument(IndexReader.java:515)
        at 
org.apache.lucene.index.IndexReader.deleteDocuments(IndexReader.java:541)
        at 
org.apache.jackrabbit.core.query.lucene.AbstractIndex.removeDocument(AbstractIndex.java:161)
        at 
org.apache.jackrabbit.core.query.lucene.PersistentIndex.removeDocument(PersistentIndex.java:105)
        at 
org.apache.jackrabbit.core.query.lucene.MultiIndex$DeleteNode.execute(MultiIndex.java:1729)
        at 
org.apache.jackrabbit.core.query.lucene.MultiIndex.executeAndLog(MultiIndex.java:858)
        at 
org.apache.jackrabbit.core.query.lucene.MultiIndex.update(MultiIndex.java:351)
        at 
org.apache.jackrabbit.core.query.lucene.SearchIndex.updateNodes(SearchIndex.java:356)
        at 
org.apache.jackrabbit.core.SearchManager.onEvent(SearchManager.java:423)
        at 
org.apache.jackrabbit.core.observation.EventConsumer.consumeEvents(EventConsumer.java:231)
        at 
org.apache.jackrabbit.core.observation.ObservationDispatcher.dispatchEvents(ObservationDispatcher.java:201)
        at 
org.apache.jackrabbit.core.observation.EventStateCollection.dispatch(EventStateCollection.java:424)
        at 
org.apache.jackrabbit.core.state.SharedItemStateManager$Update.end(SharedItemStateManager.java:721)
        at 
org.apache.jackrabbit.core.state.XAItemStateManager.commit(XAItemStateManager.java:162)
        at 
org.apache.jackrabbit.core.TransactionContext.commit(TransactionContext.java:172)
        at 
org.apache.jackrabbit.core.XASessionImpl.commit(XASessionImpl.java:315) 
[...]

This leads me to the assumption that one of those indexes listed in the field 
"indexes" in MultiIndex was somehow deleted from the file system.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to