[
https://issues.apache.org/jira/browse/SOLR-12268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16456692#comment-16456692
]
Mark Miller commented on SOLR-12268:
------------------------------------
Yeah, the IndexReader.isCurrent call in getIndexInfo.
I believe it's on by default, but also, index stats are the type of thing you
would want to poll this api for. The isCurrent info is actually not very useful
though and can significantly slow down these calls when applying deletes takes
a long time.
So the current situation is not great in two ways:
1. It's not apparent that you will hit this problem, so a user trying to
monitor index stats won't know they should turn off index info.
2. IndexInfo seems like the most likely info a monitoring system would want.
> Opening a new NRT Searcher can take a while and block calls to /admin/cores.
> ----------------------------------------------------------------------------
>
> Key: SOLR-12268
> URL: https://issues.apache.org/jira/browse/SOLR-12268
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Mark Miller
> Priority: Major
>
> When we open a new reader from a writer, we get an IndexWriter lock and may
> call applyAllDeletesAndUpdates. That call can take a while holding the lock.
> Meanwhile calls coming to /admin/cores get isCurrent for the reader, which
> checks if the IndexWriter is closed, which requires the IndexWriter lock.
> These leads to /admin/cores calls taking as long as applyAllDeletesAndUpdates.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
