[
https://issues.apache.org/jira/browse/SOLR-6246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14385893#comment-14385893
]
Varun Thacker edited comment on SOLR-6246 at 3/29/15 7:10 PM:
--------------------------------------------------------------
-I was testing out the AnalyzingInfixSuggester on trunk and noticed that with
{{<str name="buildOnStartup">false</str>}} ( which is the default ) this
problem does not happen. Only when we turned to true does a reload fail.-
-So starting Solr 5.1 setting {{<str name="buildOnStartup">false</str>}} should
be the workaround till we fix this problem-
EDIT: I was wrong. The problem still exists. Sorry for the noise.
was (Author: varunthacker):
I was testing out the AnalyzingInfixSuggester on trunk and noticed that with
{{<str name="buildOnStartup">false</str>}} ( which is the default ) this
problem does not happen. Only when we turned to true does a reload fail.
So starting Solr 5.1 setting {{<str name="buildOnStartup">false</str>}} should
be the workaround till we fix this problem
> 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: Sub-task
> Components: SearchComponents - other
> Affects Versions: 4.8, 4.8.1, 4.9
> Reporter: Varun Thacker
> Fix For: Trunk, 5.1
>
> Attachments: SOLR-6246-test.patch, SOLR-6246-test.patch,
> SOLR-6246.patch
>
>
> 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.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
