lucenenet-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Garski (JIRA)" <j...@apache.org>
Subject [jira] Commented: (LUCENENET-113) adding documents to index does, in rare cases, cause an access denied to segments.gen
Date Wed, 16 Apr 2008 16:55:21 GMT

    [ https://issues.apache.org/jira/browse/LUCENENET-113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12589645#action_12589645
] 

Michael Garski commented on LUCENENET-113:
------------------------------------------

Another process could very well be holding on to the file.  We experienced a similar issue
when Diskeeper was defragmenting a drive that contained an index that was being updated. After
disabling Diskeeper the issue was resolved.

> adding documents to index does, in rare cases, cause an access denied to segments.gen
> -------------------------------------------------------------------------------------
>
>                 Key: LUCENENET-113
>                 URL: https://issues.apache.org/jira/browse/LUCENENET-113
>             Project: Lucene.Net
>          Issue Type: Bug
>         Environment: Windows 2003
> Lucene.Net 2.1.0.3
>            Reporter: Pauli Østerø
>            Priority: Critical
>
> When updating an index via an indexwriter, does cause an access denied for segments.gen.
> After investigation with FileMon the problem seems to be Lucene deleting and creating
the segments.gen with such a speed, that Windows occasionally reports "DELETE PEND" when trying
to open the file, which causes Lucene to crash.
> A quick fix has been to do a try-catch when adding documents, and sleeping the thread
for 100 ms when encountering the UnathorizedException and trying to add the document again.

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


Mime
View raw message