[
https://issues.apache.org/jira/browse/LUCENE-2762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13041075#comment-13041075
]
Josef commented on LUCENE-2762:
-------------------------------
{quote}
Unless: Josef, are you regularly hitting exceptions somewhere....?
{quote}
No, we don't get any exceptions. I'll do some testing with our Glassfish
integration and also make sure, my test scenario matches the concrete
application integration. Hope this will isolate our problem. I'll report back
here.
> Don't leak deleted open file handles with pooled readers
> --------------------------------------------------------
>
> Key: LUCENE-2762
> URL: https://issues.apache.org/jira/browse/LUCENE-2762
> Project: Lucene - Java
> Issue Type: Bug
> Affects Versions: 2.9.4, 3.0.3, 3.1, 4.0
> Reporter: Michael McCandless
> Assignee: Michael McCandless
> Fix For: 2.9.4, 3.0.3, 3.1, 4.0
>
> Attachments: LUCENE-2762.patch
>
>
> If you have CFS enabled today, and pooling is enabled (either directly
> or because you've pulled an NRT reader), IndexWriter will hold open
> SegmentReaders against the non-CFS format of each merged segment.
> So even if you close all NRT readers you've pulled from the writer,
> you'll still see file handles open against files that have been
> deleted.
> This count will not grow unbounded, since it's limited by the number
> of segments in the index, but it's still a serious problem since the
> app had turned off CFS in the first place presumably to avoid risk of
> too-many-open-files. It's also bad because it ties up disk space
> since these files would otherwise be deleted.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
