[
https://issues.apache.org/jira/browse/SOLR-6246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15822691#comment-15822691
]
jefferyyuan edited comment on SOLR-6246 at 1/14/17 5:15 AM:
------------------------------------------------------------
I tested with the latest build - solr-6.4.0-222,reloading collection/cores with
AnalyzingInfixSuggester still failed with LockObtainFailedException.
It failed with same error even after after solr.
It can be easily reproduced, add a suggest component, then ***build the
suggester***: suggest?suggest.build=true. Then reload collection or cores.
- Seems the key to reproduce the issue is we need build the suggester.
<searchComponent name="suggest" class="solr.SuggestComponent">
<lst name="suggester">
<str name="name">infixSuggester</str>
<str name="lookupImpl">BlendedInfixLookupFactory</str>
<str
name="dictionaryImpl">DocumentDictionaryFactory</str>
<str name="blenderType">position_linear</str>
<str name="field">suggester</str>
<str name="contextField">suggesterContextField</str>
<str name="minPrefixChars">4</str>
<str name="suggestAnalyzerFieldType">textSuggest</str>
<str name="indexPath">infix_suggestions</str>
<str name="highlight">true</str>
<str name="buildOnStartup">false</str>
<str name="buildOnCommit">false</str>
</lst>
</searchComponent>
<requestHandler name="/suggest" class="solr.SearchHandler"
>
<lst name="defaults">
<str name="suggest">true</str>
<str name="suggest.dictionary">infixSuggester</str>
<str name="suggest.onlyMorePopular">true</str>
<str name="suggest.count">10</str>
<str name="suggest.collate">true</str>
</lst>
<arr name="components">
<str>suggest</str>
</arr>
</requestHandler>
was (Author: yuanyun.cn):
I tested with the latest build - solr-6.4.0-222,reloading collection/cores with
AnalyzingInfixSuggester still failed with LockObtainFailedException.
It failed with same error even after after solr.
It can be easily reproduced, add a suggest component, then build the suggester:
suggest?suggest.build=true. Then reload collection or cores/
<searchComponent name="suggest" class="solr.SuggestComponent">
<lst name="suggester">
<str name="name">infixSuggester</str>
<str name="lookupImpl">BlendedInfixLookupFactory</str>
<str
name="dictionaryImpl">DocumentDictionaryFactory</str>
<str name="blenderType">position_linear</str>
<str name="field">suggester</str>
<str name="contextField">suggesterContextField</str>
<str name="minPrefixChars">4</str>
<str name="suggestAnalyzerFieldType">textSuggest</str>
<str name="indexPath">infix_suggestions</str>
<str name="highlight">true</str>
<str name="buildOnStartup">false</str>
<str name="buildOnCommit">false</str>
</lst>
</searchComponent>
<requestHandler name="/suggest" class="solr.SearchHandler"
>
<lst name="defaults">
<str name="suggest">true</str>
<str name="suggest.dictionary">infixSuggester</str>
<str name="suggest.onlyMorePopular">true</str>
<str name="suggest.count">10</str>
<str name="suggest.collate">true</str>
</lst>
<arr name="components">
<str>suggest</str>
</arr>
</requestHandler>
> 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, 5.0, 5.1, 5.2, 5.3, 5.4
> Reporter: Varun Thacker
> Attachments: SOLR-6246.patch, SOLR-6246-test.patch,
> SOLR-6246-test.patch, SOLR-6246-test.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]