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. -Gus
