[
https://issues.apache.org/jira/browse/SOLR-3222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Russell Black updated SOLR-3222:
--------------------------------
Description:
Ever wondered what queries to use to prime your cache? This patch allows you
to query a warm running instance for a list of warming queries. The list is
generated from the server's caches, meaning you get back an optimal set of
queries. The set is optimal to the extent that the caches are optimized. The
queries are returned in a format that can be consumed by the
{code:xml}<listener event="firstSearcher"
class="solr.QuerySenderListener">{code} section of {{solrconfig.xml}}.
One can use this feature to generate a static set of good warming queries to
place in {{solrconfig.xml}} under {code:xml}<listener event="firstSearcher"
class="solr.QuerySenderListener">{code}
It can even be used in a dynamic fashion like this:
{code:xml}
<listener event="firstSearcher" class="solr.QuerySenderListener">
<xi:include href="http://host/solr/core/autowarm"; xpointer="element(/1/2)"
xmlns:xi="http://www.w3.org/2001/XInclude"/>
</listener>
{code}
which can work well in certain distributed load-balanced architectures,
although in production it would be wise to add an {{<xi:fallback>}} element to
the include in the event that the host is down.
I implemented this by introducing a new request handler:
{code:xml}
<requestHandler name="/autowarm" class="solr.AutoWarmRequestHandler" />
{code}
The request handler pulls a configurable number of "top" keys from the
{{filterCache}},{{fieldValueCache}}, and {{queryResultCache}}. For each key,
it constructs a query that will cause that key to be placed in the associated
cache. The list of constructed queries are then returned in the response.
Patch to follow.
was:
Ever wondered what queries to use to prime your cache? This patch allows you
to query a warm running instance for a list of warming queries. The list is
generated from the server's caches, meaning you get back an optimal set of
queries. The set is optimal to the extent that the caches are optimized. The
queries are returned in a format that can be consumed by the
{code:xml}<listener event="firstSearcher"
class="solr.QuerySenderListener">{code} section of {{solrconfig.xml}}.
One can use this feature to generate a static set of good warming queries to
place in {{solrconfig.xml}} under {code:xml}<listener event="firstSearcher"
class="solr.QuerySenderListener">{code}
It can even be used in a dynamic faction like this:
{code:xml}
<listener event="firstSearcher" class="solr.QuerySenderListener">
<xi:include href="http://host/solr/core/autowarm"; xpointer="element(/1/2)"
xmlns:xi="http://www.w3.org/2001/XInclude"/>
</listener>
{code}
which can work well in certain distributed load-balanced architectures,
although in production it would be wise to add an {{<xi:fallback>}} element to
the include in the event that the host is down.
I implemented this by introducing a new request handler:
{code:xml}
<requestHandler name="/autowarm" class="solr.AutoWarmRequestHandler" />
{code}
The request handler pulls a configurable number of "top" keys from the
{{filterCache}},{{fieldValueCache}}, and {{queryResultCache}}. For each key,
it constructs a query that will cause that key to be placed in the associated
cache. The list of constructed queries are then returned in the response.
Patch to follow.
> Pull optimal cache warming queries from a warm solr instance
> ------------------------------------------------------------
>
> Key: SOLR-3222
> URL: https://issues.apache.org/jira/browse/SOLR-3222
> Project: Solr
> Issue Type: New Feature
> Components: search
> Affects Versions: 3.5, 4.0
> Reporter: Russell Black
> Labels: patch, performance
>
> Ever wondered what queries to use to prime your cache? This patch allows you
> to query a warm running instance for a list of warming queries. The list is
> generated from the server's caches, meaning you get back an optimal set of
> queries. The set is optimal to the extent that the caches are optimized.
> The queries are returned in a format that can be consumed by the
> {code:xml}<listener event="firstSearcher"
> class="solr.QuerySenderListener">{code} section of {{solrconfig.xml}}.
> One can use this feature to generate a static set of good warming queries to
> place in {{solrconfig.xml}} under {code:xml}<listener event="firstSearcher"
> class="solr.QuerySenderListener">{code}
> It can even be used in a dynamic fashion like this:
> {code:xml}
> <listener event="firstSearcher" class="solr.QuerySenderListener">
> <xi:include href="http://host/solr/core/autowarm"; xpointer="element(/1/2)"
> xmlns:xi="http://www.w3.org/2001/XInclude"/>
> </listener>
> {code}
> which can work well in certain distributed load-balanced architectures,
> although in production it would be wise to add an {{<xi:fallback>}} element
> to the include in the event that the host is down.
> I implemented this by introducing a new request handler:
> {code:xml}
> <requestHandler name="/autowarm" class="solr.AutoWarmRequestHandler" />
> {code}
> The request handler pulls a configurable number of "top" keys from the
> {{filterCache}},{{fieldValueCache}}, and {{queryResultCache}}. For each key,
> it constructs a query that will cause that key to be placed in the associated
> cache. The list of constructed queries are then returned in the response.
> Patch to follow.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
