You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Tomás Fernández Löbbe (JIRA)" <ji...@apache.org> on 2016/06/23 21:25:16 UTC
[jira] [Commented] (SOLR-9244) Lots of "Previous SolrRequestInfo
was not closed" in Solr log
[ https://issues.apache.org/jira/browse/SOLR-9244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15347229#comment-15347229 ]
Tomás Fernández Löbbe commented on SOLR-9244:
---------------------------------------------
Probably the same issue as reported in SOLR-8657. If so, we can close this one as duplicate and update the affected versions in SOLR-8657.
> Lots of "Previous SolrRequestInfo was not closed" in Solr log
> -------------------------------------------------------------
>
> Key: SOLR-9244
> URL: https://issues.apache.org/jira/browse/SOLR-9244
> Project: Solr
> Issue Type: Bug
> Components: Server
> Affects Versions: 5.3.1
> Reporter: Gary Lee
> Priority: Minor
> Fix For: 5.3.1
>
>
> After upgrading to Solr 5.3.1, we started seeing a lot of "Previous SolrRequestInfo was not closed" ERROR level messages in the logs. Upon further inspection, it appears this is a sanity check and not an error that needs attention. It appears that the SolrRequestInfo isn't freed in one particular path (no corresponding call to SolrRequestInfo.clearRequestInfo in HttpSolrCall.call), which often leads to a lot of these messages.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org