[ 
https://issues.apache.org/jira/browse/LUCENE-2280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12842244#action_12842244
 ] 

Michael McCandless commented on LUCENE-2280:
--------------------------------------------

bq.  However, indexing failed again and the index file was again deleted. 

Are you calling .commit() periodically?  It's odd, otherwise, that you have no 
index on hitting any problem.  (It's not necessary to call commit until the 
very end, if you don't need readers to see the ongoing changes, don't need the 
durability, etc.).

bq. I am not sure if deletion of the index file when these exceptions are 
thrown, is the right behaviour.
bq. Stack trace: java.io.FileNotFoundException: index_21f.fdt (The system 
cannot find the file specified.)

Lucene isn't "intentionally" deleting files that are referenced by the commit.  
But if you're not committing during the whole IW session, then you'd see no 
index at the end.

But, this FNFE is not expected in any event.  Seeing the full infoStream 
leading to this may help...

That FNFE is happening as IW tries to build the CFS of the segment flushed 
during close.

Are you using autoCommit=true or false?

The fact that this only happens on Windows is telling.... is there a virus 
checker running on this machine?

It'd also be good to know if this still happens on newer versions of Lucene.

> IndexWriter.optimize() throws NullPointerException
> --------------------------------------------------
>
>                 Key: LUCENE-2280
>                 URL: https://issues.apache.org/jira/browse/LUCENE-2280
>             Project: Lucene - Java
>          Issue Type: Bug
>          Components: Index
>    Affects Versions: 2.3.2
>         Environment: Win 2003, lucene version 2.3.2, IBM JRE 1.6
>            Reporter: Ritesh Nigam
>         Attachments: lucene.jar
>
>
> I am using lucene 2.3.2 search APIs for my application, i am indexing 45GB 
> database which creates approax 200MB index file, after finishing the indexing 
> and while running optimize() i can see NullPointerExcception thrown in my log 
> and index file is getting corrupted, log says
> ------------------------------------------------------------------------
> Caused by: 
> java.lang.NullPointerException
>       at 
> org.apache.lucene.store.BufferedIndexOutput.writeBytes(BufferedIndexOutput.java:49)
>       at org.apache.lucene.store.IndexOutput.writeBytes(IndexOutput.java:40)
>       at 
> org.apache.lucene.index.SegmentMerger.mergeNorms(SegmentMerger.java:566)
>       at org.apache.lucene.index.SegmentMerger.merge(SegmentMerger.java:135)
>       at 
> org.apache.lucene.index.IndexWriter.mergeMiddle(IndexWriter.java:3273)
>       at org.apache.lucene.index.IndexWriter.merge(IndexWriter.java:2968)
>       at 
> org.apache.lucene.index.ConcurrentMergeScheduler$MergeThread.run(ConcurrentMergeScheduler.java:240)
> ------------------------------------------------------------------------
> and this is happening quite frequently, although I am not able to reproduce 
> it on demand, I saw an issue logged which is some what related to mine issue 
> (http://mail-archives.apache.org/mod_mbox/lucene-solr-user/200809.mbox/%3c6e4a40db-5efc-42da-a857-d59f4ec34...@mikemccandless.com%3e)
>  but the only difference here is I am not using Store.Compress for my fields, 
> i am using Store.NO instead. please note that I am using IBM JRE for my 
> application.
> Is this an issue with lucene?, if yes it is fixed in which version?

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


---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-dev-h...@lucene.apache.org

Reply via email to