lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tomás Fernández Löbbe (JIRA) <>
Subject [jira] [Updated] (SOLR-6845) figure out why suggester causes slow startup - even when not used
Date Tue, 20 Jan 2015 21:29:36 GMT


Tomás Fernández Löbbe updated SOLR-6845:
    Attachment: SOLR-6845.patch

Here is a new patch. I saw that we were trying to load the suggester twice, once on the Suggester
init and once in the searcher listener. I removed the load from the searcher listener. 
I also changed the default of the "buildOnStartup", instead of being always "false", it defaults
to true if no suggester dictionary exists (if the storeDir is not set or if it's set but the
suggester was never built). This is compatible with the behavior in 4.10. 
Unfortunately I didn't have time to put this change in 5.0, there are no major compatibility
issues, the only one I see is that "reload" no longer builds if the dictionary is not present.
I think this is correct and should be the behavior of 6.x, for 5.x I'll make the reload action
build if no dictionary is present.

> figure out why suggester causes slow startup - even when not used
> -----------------------------------------------------------------
>                 Key: SOLR-6845
>                 URL:
>             Project: Solr
>          Issue Type: Bug
>            Reporter: Hoss Man
>         Attachments: SOLR-6845.patch, SOLR-6845.patch, 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
> ...
> 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

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message