[
https://issues.apache.org/jira/browse/SOLR-6845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tomás Fernández Löbbe updated SOLR-6845:
----------------------------------------
Attachment: SOLR-6845.patch
Here is a patch to add buildOnStartup. With buildOnStartup=false and
buildOnCommit=true, the suggester is loaded if it already exist, but not built
if it doesn't on startup.
The problem I see is that in regular core reload, searchers are open in a way
that the "newSearcherListeners" are invoked, this means that even if
buildOnStartup=false and buildOnCommit=true, a core reload would build the
suggester if not found
> figure out why suggester causes slow startup - even when not used
> -----------------------------------------------------------------
>
> Key: SOLR-6845
> URL: https://issues.apache.org/jira/browse/SOLR-6845
> Project: Solr
> Issue Type: Bug
> Reporter: Hoss Man
> Attachments: SOLR-6845.patch
>
>
> SOLR-6679 was filed to track the investigation into the following problem...
> {panel}
> The stock solrconfig provides a bad experience with a large index... start up
> Solr and it will spin at 100% CPU for minutes, unresponsive, while it
> apparently builds a suggester index.
> ...
> This is what I did:
> 1) indexed 10M very small docs (only takes a few minutes).
> 2) shut down Solr
> 3) start up Solr and watch it be unresponsive for over 4 minutes!
> I didn't even use any of the fields specified in the suggester config and I
> never called the suggest request handler.
> {panel}
> ..but ultimately focused on removing/disabling the suggester from the sample
> configs.
> Opening this new issue to focus on actually trying to identify the root
> problem & fix it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
