lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "B.Nicolotti (JIRA)" <>
Subject [jira] [Commented] (LUCENE-4467) SegmentReader.loadDeletedDocs FileNotFoundExceptio load _hko_7.del - corrupted index
Date Wed, 14 Nov 2012 15:42:12 GMT


B.Nicolotti commented on LUCENE-4467:

We left only one web applicatin writing the index with a LockTimeOut of 120s, but we've got
a problem:

Fri Oct 26 10:08:02 CEST 2012:com.siap.WebServices.Utility.UtiIndexerLucene caught an exception:
 e.toString() /usr/local/WS_DynPkg/logs/index/_8c0_2c.del (No
such file or directory),
 e.getMessage():/usr/local/WS_DynPkg/logs/index/_8c0_2c.del (No such file or directory) Method)<init>($SimpleFSIndexInput$Descriptor.<init>($SimpleFSIndexInput.<init>($NIOFSIndexInput.<init>(

Fri Oct 26 10:10:02 CEST 2012:com.siap.WebServices.Utility.UtiIndexerLucene

indexing:/usr/local/WS_DynPkg/logs//log_2012-10-26.20121026100648672-1.log caught an exception:
 e.toString() Lock obtain timed out: NativeFSLock@/usr/local/WS_DynPkg/logs/index/write.lock,
 e.getMessage():Lock obtain timed out: NativeFSLock@/usr/local/WS_DynPkg/logs/index/write.lock

and the index is no longer useable. The index seems very sensitive, but we've implemented
the indexing only once after writing to logs, and so if the index is broken we've to erase
the index

What do you suggest?

Is it possibile to set an infinite waiting time to get the write.lock?

Many thanks

Best regards

> SegmentReader.loadDeletedDocs FileNotFoundExceptio load _hko_7.del - corrupted index
> ------------------------------------------------------------------------------------
>                 Key: LUCENE-4467
>                 URL:
>             Project: Lucene - Core
>          Issue Type: Bug
>    Affects Versions: 3.6
>         Environment: Currently using:
> java -version
> java version "1.5.0_13"
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_13-b05)
> Java HotSpot(TM) Client VM (build 1.5.0_13-b05, mixed mode, sharing)
> Tomcat 5.5
> lucene 3.6.0
>            Reporter: B.Nicolotti
>         Attachments:
> We're using lucene to index XML. We've had it in test on a server for some weeks with
no problem, but today we've got the error below and the index seems no longer usable.
> Could you please tell us 
> 1) is there a way to recover the index?
> 2) is there a way to avoid this error?
> I can supply the index if needed
> many thanks
> Tue Oct 09 17:41:02 CEST 2012:com.siap.WebServices.Utility.UtiIndexerLucene caught an
exception: 32225010
>  e.toString() /usr/local/WS_DynPkg/logs/index/_hko_7.del
(No such file or directory),
>  e.getMessage():/usr/local/WS_DynPkg/logs/index/_hko_7.del (No such file or directory)
> Method)
> org.apache.lucene.util.BitVector.<init>(
> org.apache.lucene.index.SegmentReader.loadDeletedDocs(
> org.apache.lucene.index.SegmentReader.get(
> org.apache.lucene.index.IndexWriter$ReaderPool.get(
> org.apache.lucene.index.IndexWriter$ReaderPool.get(
> org.apache.lucene.index.BufferedDeletesStream.applyDeletes(
> org.apache.lucene.index.IndexWriter.doFlush(
> org.apache.lucene.index.IndexWriter.flush(
> org.apache.lucene.index.IndexWriter.closeInternal(
> org.apache.lucene.index.IndexWriter.close(
> org.apache.lucene.index.IndexWriter.close(
> com.siap.WebServices.Utility.UtiIndexerLucene.delete(
> com.siap.WebServices.Utility.UtiIndexerLucene.indexFile(

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message