[
https://issues.apache.org/jira/browse/SOLR-14657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17170338#comment-17170338
]
ASF subversion and git services commented on SOLR-14657:
--------------------------------------------------------
Commit 64d1f9144bae0eb7b209e89545e86d654ffce2f5 in lucene-solr's branch
refs/heads/branch_8x from Chris M. Hostetter
[ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=64d1f91 ]
SOLR-14657: Improve error handling in IndexReader realted metrics that were
causing scary ERROR logging if metrics were requested while Solr was in the
process of closing/re-opening a new IndexReader
(cherry picked from commit a6c058a26094bf169320d09e9fa1eff7faa5f432)
> spurious ERRORs due to race condition between SolrIndexSearcher metrics and
> IndexReader closing
> -----------------------------------------------------------------------------------------------
>
> Key: SOLR-14657
> URL: https://issues.apache.org/jira/browse/SOLR-14657
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Chris M. Hostetter
> Assignee: Chris M. Hostetter
> Priority: Major
> Attachments: SOLR-14657.patch, SOLR-14657.patch
>
>
> I've seen situations in the wild where systems monitoring/polling metrics can
> trigger scary looking - but otherwise benign - ERRORs due to
> AlreadyClosedExceptions if/when the searcher/reader is in the process of
> being re-opened and the Gauge tries to call reader.numDocs(), etc...
> We should tweak the metrics logic to just ignore these exceptions
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
