You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Shai Erera (Created) (JIRA)" <ji...@apache.org> on 2012/02/18 06:55:59 UTC
[jira] [Created] (LUCENE-3798) Potential IndexReader leak in
SearcherManager and NRTManager
Potential IndexReader leak in SearcherManager and NRTManager
------------------------------------------------------------
Key: LUCENE-3798
URL: https://issues.apache.org/jira/browse/LUCENE-3798
Project: Lucene - Java
Issue Type: Bug
Components: core/search
Reporter: Shai Erera
Priority: Critical
Fix For: 3.6, 4.0
SearcherManager and NRTManager ctors init a new IndexReader and call searcherFactory.newSearcher. The latter can throw IOE,in which case we fail to close the readers. We should wrap the code with a try-finally (success) clause.
Opening this issue so we don't forget to fix it.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Resolved] (LUCENE-3798) Potential IndexReader leak in
SearcherManager and NRTManager
Posted by "Shai Erera (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LUCENE-3798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Shai Erera resolved LUCENE-3798.
--------------------------------
Resolution: Invalid
Fix Version/s: (was: 3.6)
(was: 4.0)
Argh, you're right. I didn't 'svn up' before I looked at the code :).
Sorry for the noise.
> Potential IndexReader leak in SearcherManager and NRTManager
> ------------------------------------------------------------
>
> Key: LUCENE-3798
> URL: https://issues.apache.org/jira/browse/LUCENE-3798
> Project: Lucene - Java
> Issue Type: Bug
> Components: core/search
> Reporter: Shai Erera
> Priority: Critical
>
> SearcherManager and NRTManager ctors init a new IndexReader and call searcherFactory.newSearcher. The latter can throw IOE,in which case we fail to close the readers. We should wrap the code with a try-finally (success) clause.
> Opening this issue so we don't forget to fix it.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (LUCENE-3798) Potential IndexReader leak in
SearcherManager and NRTManager
Posted by "Michael McCandless (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LUCENE-3798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13210895#comment-13210895 ]
Michael McCandless commented on LUCENE-3798:
--------------------------------------------
I think this is fixed with the new getSearcher (static) method? (It decRefs the incoming reader on exception...)
> Potential IndexReader leak in SearcherManager and NRTManager
> ------------------------------------------------------------
>
> Key: LUCENE-3798
> URL: https://issues.apache.org/jira/browse/LUCENE-3798
> Project: Lucene - Java
> Issue Type: Bug
> Components: core/search
> Reporter: Shai Erera
> Priority: Critical
> Fix For: 3.6, 4.0
>
>
> SearcherManager and NRTManager ctors init a new IndexReader and call searcherFactory.newSearcher. The latter can throw IOE,in which case we fail to close the readers. We should wrap the code with a try-finally (success) clause.
> Opening this issue so we don't forget to fix it.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org