[
https://issues.apache.org/jira/browse/LUCENE-2255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12831095#action_12831095
]
Jason Rutherglen commented on LUCENE-2255:
------------------------------------------
You're not the first to report this... I wonder if we should also do a weak ref
type of dealie that auto closes the reader for users who aren't calling
IR.close?
To answer the question, yes, close on IR must be called. I can't directly do
anything about the javadocs so I'll leave that for Mike.
> IndexWriter.getReader() allocates file handles
> ----------------------------------------------
>
> Key: LUCENE-2255
> URL: https://issues.apache.org/jira/browse/LUCENE-2255
> Project: Lucene - Java
> Issue Type: Bug
> Components: Index
> Environment: Ubuntu 9.10, Java 6
> Reporter: Mikkel Kamstrup Erlandsen
> Attachments: LuceneManyCommits.java
>
>
> I am not sure if this is a "bug" or really just me not reading the Javadocs
> right...
> The IR returned by IW.getReader() leaks file handles if you do not close()
> it, leading to starvation of the available file handles/process. If it was
> clear from the docs that this was a *new* reader and not some reference owned
> by the writer then this would probably be ok. But as I read the docs the
> reader is internally managed by the IW, which at first shot lead me to
> believe that I shouldn't close it.
> So perhaps the docs should be amended to clearly state that this is a
> caller-owns reader that *must* be closed? Attaching a simple app that
> illustrates the problem.
--
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
