lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christopher Gross <cogr...@gmail.com>
Subject Re: XSLT Caching Warning
Date Fri, 02 May 2014 01:30:11 GMT
The message implies that there is a better way of having XSLT
transformations.  Is that the case, or is there just this perpetual warning
for normal operations?

-- Chris


On Thu, May 1, 2014 at 5:08 PM, Ahmet Arslan <iorixxx@yahoo.com> wrote:

> Hi Chris,
>
> Looking at source code reveals that warning message printed always.
> Independent of xsltCacheLifetimeSeconds value.
>
>
>  /** singleton */
>   private TransformerProvider() {
>     // tell'em: currently, we only cache the last used XSLT transform, and
> blindly recompile it
>     // once cacheLifetimeSeconds expires
>     log.warn(
>         "The TransformerProvider's simplistic XSLT caching mechanism is
> not appropriate "
>         + "for high load scenarios, unless a single XSLT transform is used"
>         + " and xsltCacheLifetimeSeconds is set to a sufficiently high
> value."
>     );
>   }
>
>
>
>
>
> On Thursday, May 1, 2014 11:29 PM, Christopher Gross <cogross@gmail.com>
> wrote:
> I get this warning when Solr (4.7.2) Starts:
> WARN  org.apache.solr.util.xslt.TransformerProvider  รข The
> TransformerProvider's simplistic XSLT caching mechanism is not appropriate
> for high load scenarios, unless a single XSLT transform is used and
> xsltCacheLifetimeSeconds is set to a sufficiently high value.
>
> The solrconfig.xml setting is:
>   <queryResponseWriter name="xslt" class="solr.XSLTResponseWriter">
>     <int name="xsltCacheLifetimeSeconds">100000</int>
>   </queryResponseWriter>
>
> Is there a different class that I should be using?  Is there a higher
> number than 100000 that will do the trick?
>
> Thanks!
>
> -- Chris
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message