[
https://issues.apache.org/jira/browse/LUCENE-425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12543081
]
cbowditch edited comment on LUCENE-425 at 11/16/07 6:13 AM:
-----------------------------------------------------------------
We have been using Lucene 1.9.1 for the past 2 years and this issue occurs on a
regular basis. Always on Windows and more often on machines with slower hard
disks, i.e. Laptops. A colleague of mine downloaded the source and patched it
to retry the rename and delete operations several times before giving up. This
works well on our environments so we would like to get the change into Trunk
code.
I will prepare a patch against trunk shortly which will solve the problem.
was (Author: cbowditch):
We have been using Lucene 1.9.1 for the past 2 years and this issue occurs
on a regular basis. Always on Windows and more often on machines with slower
hard disks, i.e. Laptops. A colleague of my downloaded the source and patched
it to retry the rename and delete operations several times before giving up. I
will prepare a patch against trunk shortly which will solve the problem.
> "Cannot rename segments.new to segments"
> ----------------------------------------
>
> Key: LUCENE-425
> URL: https://issues.apache.org/jira/browse/LUCENE-425
> Project: Lucene - Java
> Issue Type: Bug
> Components: Index
> Affects Versions: 1.4
> Environment: Operating System: Windows XP
> Platform: PC
> Reporter: Mikko Noromaa
>
> AddDocument periodically fails with "Cannot rename segments.new to segments".
> Sometimes it happens after 10,000 documents, sometimes after 200,000
> documents.
> My index is placed on a FAT partition. My Lucene version is 1.4.3. I am using
> a single IndexWriter object and doing all AddDocuments calls serially from a
> single thread.
> I saw some discussion about this problem in the mailing lists, but looks like
> the problem wasn't completely eliminated yet.
> My suggested solutions are as follows:
> - If renameTo() fails, wait some time and retry. After this, apply the other
> methods that are now in FSDirectory.java. Retry them as well after waiting
> for
> some time.
> - In the IndexWriter constructor, check for 'segments.new' if 'segments'
> cannot be found. This would allow recovery if FSDirectory failed on a
> previous
> run. Now I have to write the recovery code myself outside of Lucene.
--
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
