Re: XSLT Caching Warning
I have a few transforms that I need to do, but I turned set the cache lifetime very high. I'm just trying to rectify error messages that pop up. If it's something that I can ignore, then that's OK, I just wanted to be sure. Thanks! -- Chris On Thu, May 1, 2014 at 10:32 PM, Alexandre Rafalovitch wrote: > I think the key message here is: > "simplistic XSLT caching mechanism is not appropriate for high load > scenarios". > > As in, maybe this is not really a production-level component. One > exception is given and it is not just lifetime, it's also a > single-transform. > > Are you satisfying both of those conditions? If so, it's probably ok > to just ignore the warning. > > Regards, >Alex. > Personal website: http://www.outerthoughts.com/ > Current project: http://www.solr-start.com/ - Accelerating your Solr > proficiency > > > On Fri, May 2, 2014 at 3:28 AM, Christopher Gross > 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: > > > > 10 > > > > > > Is there a different class that I should be using? Is there a higher > > number than 10 that will do the trick? > > > > Thanks! > > > > -- Chris >
Re: XSLT Caching Warning
I think the key message here is: "simplistic XSLT caching mechanism is not appropriate for high load scenarios". As in, maybe this is not really a production-level component. One exception is given and it is not just lifetime, it's also a single-transform. Are you satisfying both of those conditions? If so, it's probably ok to just ignore the warning. Regards, Alex. Personal website: http://www.outerthoughts.com/ Current project: http://www.solr-start.com/ - Accelerating your Solr proficiency On Fri, May 2, 2014 at 3:28 AM, Christopher Gross 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: > > 10 > > > Is there a different class that I should be using? Is there a higher > number than 10 that will do the trick? > > Thanks! > > -- Chris
Re: XSLT Caching Warning
On 5/1/2014 7:30 PM, Christopher Gross wrote: > 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? When I was using XSLT, I got a warning for every core, even though I had a cached lifetime that would prevent problems. I don't remember what that lifetime was any more, probably at least five minutes, but it might have been longer. I also met the other criteria -- there was only one XSLT defined. Perhaps the warning needs to be suppressed if the lifetime is above a certain value and there is only one transform defined? I would expect that even 60 seconds would be a long enough lifetime to prevent major issues in high load scenarios ... but we could bikeshed that number forever. Thanks, Shawn
Re: XSLT Caching Warning
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 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
> 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:
>
> 10
>
>
> Is there a different class that I should be using? Is there a higher
> number than 10 that will do the trick?
>
> Thanks!
>
> -- Chris
>
Re: XSLT Caching Warning
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 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:
10
Is there a different class that I should be using? Is there a higher
number than 10 that will do the trick?
Thanks!
-- Chris
XSLT Caching Warning
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: 10 Is there a different class that I should be using? Is there a higher number than 10 that will do the trick? Thanks! -- Chris
