[
https://issues.apache.org/jira/browse/SOLR-6845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14247039#comment-14247039
]
Hoss Man commented on SOLR-6845:
--------------------------------
bq. We should just comment out the <str name="q">static firstSearcher warming
in solrconfig.xml</str> query ...
This is still side stepping the root problem this issue was opened to address:
why is hte /suggest handler so damn slow?
We don't need more baind-aid fixes that can be applied to the techproducts
example configs to work-arround whatever fundemental problem exists - SOLR-6679
already applied enough of a band-aid for that.
what we need is to understand:
* why the hell is this suggester so damn slow to build it's dictionary even
when the fields aren't used at all in the index?
* why the does this suggester auto-register a firstSearcher/newSearcher event
listener to build the dict w/o there being any sort of configuration option
indicating that the solr-admin has *requested* it to build on firstSearcher (or
on every searcher open if that's what/why this is happening)
> 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
>
> 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]
