lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Shawn Heisey <>
Subject Re: Sharing a class across cores
Date Wed, 11 Nov 2015 23:54:14 GMT
On 11/11/2015 4:11 PM, Gus Heck wrote:
> I have a case where a component loads up a large CSV file (2.5 million
> lines) to build a map. This worked ok in a case where we had a single
> core, but it isn't working so well with 40 cores because each core loads
> a new copy of the component in a new classloader and I get 40 new
> versions of the same class each holding it's own private static final
> map (one for each core). Each line is small, but a billion of anything
> gets kinda heavy. Is this the intended class loading behavior?
> Is there some where that one can cause a class to be loaded in a parent
> classloader above the core so that it's loaded just once? I want to load
> it in some way that leverages standard solr resource loading, so that
> I'm not hard coding or setting sysprops just to be able to find it.
> This is in a copy of trunk from about a month ago... so 6.x stuff is
> mostly available.

This sounds like a question that I just recently answered on IRC.

If you remove all <lib> elements from your solrconfig.xml files and
place all extra jars for Solr into ${solr.solr.home}/lib ... Solr will
load those jars before any cores are created and they will be available
to all cores.

There is a minor bug with this that will be fixed in Solr 5.4.0.  It is
unlikely that this will affect third-party components, but be aware that
until 5.4, jars in that lib directory will be loaded twice by older 5.x


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message