lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael McCandless (JIRA)" <j...@apache.org>
Subject [jira] Closed: (LUCENE-425) "Cannot rename segments.new to segments"
Date Fri, 10 Nov 2006 11:24:40 GMT
     [ http://issues.apache.org/jira/browse/LUCENE-425?page=all ]

Michael McCandless closed LUCENE-425.
-------------------------------------

    Resolution: Duplicate
      Assignee:     (was: Lucene Developers)


I think this one is a dup of LUCENE-665

The intermittant errors on WIN32 came down to 3rd party software that can open files shortly
after they were created, thus preventing rename from succeeding.  The combination of native
LockFactor implementation (LUCENE-678 ) and Lockless commits (LUCENE-701 ) should resolve
these issues.

> "Cannot rename segments.new to segments"
> ----------------------------------------
>
>                 Key: LUCENE-425
>                 URL: http://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.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

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


Mime
View raw message