[
https://issues.apache.org/jira/browse/SOLR-6246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14100514#comment-14100514
]
Varun Thacker commented on SOLR-6246:
-------------------------------------
bq. When we call Solr's reload command, a new instance of
AnalyzingInfixSuggester is created. When trying to create a new writer on the
same Directory a lock cannot be obtained and Solr fails to reload the core.
SolrSuggester adds close hooks but that doesn't work in this case. The reason
is that the close hooks gets called only after the new core gets created.
CoreContainer.reload() first creates the new core ( which fails ) and only
after it has registered the new core does it clean up the old core (
registerCore() )
We need to clean up the resources before the new core is created or use the
same resources again if it hasn't changed.
> Core fails to reload when AnalyzingInfixSuggester is used as a Suggester
> ------------------------------------------------------------------------
>
> Key: SOLR-6246
> URL: https://issues.apache.org/jira/browse/SOLR-6246
> Project: Solr
> Issue Type: Bug
> Affects Versions: 4.8, 4.8.1, 4.9
> Reporter: Varun Thacker
> Fix For: 5.0, 4.10
>
>
> LUCENE-5477 - added near-real-time suggest building to
> AnalyzingInfixSuggester. One of the changes that went in was a writer is
> persisted now to support real time updates via the add() and update() methods.
> When we call Solr's reload command, a new instance of AnalyzingInfixSuggester
> is created. When trying to create a new writer on the same Directory a lock
> cannot be obtained and Solr fails to reload the core.
> Also when AnalyzingInfixLookupFactory throws a RuntimeException we should
> pass along the original message.
> I am not sure what should be the approach to fix it. Should we have a
> reloadHook where we close the writer?
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
