On 1/3/2017 11:20 AM, Jake Gillespie wrote:
> When running on a single server, I followed the instructions here
> <https://wiki.apache.org/solr/SolrPlugins>. In short, I placed the jar
> in a directory on the server, added this directory using the sharedLib
> attribute to solr.xml and then used the lib directive in
> solrconfig.xml to point to this jar.
If you use sharedLib (which defaults to ${solr.solr.home}/lib) for this,
then you don't need the <lib> directive. Using the <lib> directive as
well as sharedLib will load the jar at least twice. Not only does this
have the potential to waste memory, but loading some jars twice will
actually break them.
For either standalone or cloud mode, just remove all lib-related config
(including sharedLib), and place all extra jars into
${solr.solr.home}/lib on every server. This location is automatically
loaded by Solr, without any config. The same goes for a lib directory
inside the core's instanceDir.
The blob store API isn't available in 4.9, and even on the versions
where it is present, will only work for classes in solrconfig.xml.
Classes in the schema won't use the blob store.
See this issue for a discussion about Solr's classloader and some of the
problems that can happen:
https://issues.apache.org/jira/browse/SOLR-4852
Thanks,
Shawn
