: nearly 100 percent and no queries were answered. I found out that
: "warming" the server with serial queries, not parallel ones, bypassed
: this problem (not to be confused with warming the caches!). So after a
Note that you can have Solr do this automatically for you in both
firstSearcher and newSearcher listeners (so you never risk having one of
your users hit the searcher before your warming queries). Take a look at
the commented out usage of QuerySenderListener in the example
solrconfig.xml...
<listener event="newSearcher" class="solr.QuerySenderListener">
<arr name="queries">
<lst> <str name="q">solr</str> <str name="start">0</str> <str
name="rows">10</str> </lst>
<lst> <str name="q">rocks</str> <str name="start">0</str> <str
name="rows">10</str> </lst>
</arr>
</listener>
-Hoss
