Lucene-Tests fail for certain file-systems
Issue #1348
invalid
Reported by bsc: Some lucene-tests related to index-generation or -management produce failures when executed for certain file-systems, because some data can not be deleted or overwritten. Probably one class is still accessing those files, while another one is trying to delete or overwrite them, resulting in a write.lock or redundant .nfs-files (see http://nfs.sourceforge.net/nfs-howto/ar01s02.html#whatis_nfs) in the index-folder, which will still be there after the test-runs are finished.
Test set: org.bibsonomy.lucene.index.manager.LuceneGoldStandardPublicationManagerTest
-------------------------------------------------------------------------------
Tests run: 2, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 29.138 sec <<< FAILURE!
testUpdate(org.bibsonomy.lucene.index.manager.LuceneGoldStandardPublicationManagerTest) Time elapsed: 4.266 sec <<< ERROR!
java.io.IOException: Cannot overwrite: [...] bibsonomy-lucenesrctestresourceslucene_GoldStandardPublication-0_1.cfs
at org.apache.lucene.store.FSDirectory.initOutput(FSDirectory.java:132)
at org.apache.lucene.store.SimpleFSDirectory.createOutput(SimpleFSDirectory.java:55)
at org.apache.lucene.index.CompoundFileWriter.close(CompoundFileWriter.java:147)
at org.apache.lucene.index.DocumentsWriter.createCompoundFile(DocumentsWriter.java:665)
at org.apache.lucene.index.IndexWriter.doFlushInternal(IndexWriter.java:3708)
at org.apache.lucene.index.IndexWriter.doFlush(IndexWriter.java:3565)
at org.apache.lucene.index.IndexWriter.flush(IndexWriter.java:3555)
at org.apache.lucene.index.IndexWriter.optimize(IndexWriter.java:2320)
at org.apache.lucene.index.IndexWriter.optimize(IndexWriter.java:2298)
at org.apache.lucene.index.IndexWriter.optimize(IndexWriter.java:2268)
at org.bibsonomy.lucene.util.generator.LuceneGenerateResourceIndex.createIndexFromDatabase(LuceneGenerateResourceIndex.java:237)
at org.bibsonomy.lucene.util.generator.LuceneGenerateResourceIndex.generateIndex(LuceneGenerateResourceIndex.java:141)
at org.bibsonomy.lucene.util.generator.LuceneGenerateResourceIndex.generateIndex(LuceneGenerateResourceIndex.java:154)
at org.bibsonomy.lucene.index.manager.LuceneGoldStandardPublicationManagerTest.initLucene(LuceneGoldStandardPublicationManagerTest.java:90)
This problem also occurs for the LuceneUpdateManagerTest.
Comments (5)
-
Account Deleted -
- changed status to open
-
- changed component to search
- edited description
-
- edited description
-
- changed status to invalid
replaced lucene with elasticsearch
- Log in to comment
@whoever uses such a filesystem and suffers from this: plese feel free to fix this