[SOLR-13637] Enable loading of plugins from the corecontainer memclassloader

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Invalid
• Assignee: Unassigned
• Reporter: Noble Paul
• Created: 15/Jul/19 18:17
• Updated: 06/Oct/19 21:16
• Resolved: 06/Oct/19 15:32

Description

When we update jars or add/modify plugins no core reloading should be required .Core reloading is a very expensive operation. Optionally, we can just make the plugin depend on the corecontainer level classloader.

 <queryParser name="mycustomQParser" class="my.path.to.ClassName" runtimeLib="global">
 
  </queryParser>

or alternately using the config API

curl -X POST -H 'Content-type:application/json' --data-binary '
{
  "create-queryparser": {
      "name": "mycustomQParser" ,
      "class" : "my.path.to.ClassName",
     "runtimeLib" : "global"
  }
}' http://localhost:8983/api/c/mycollection/config

The global classloader is the corecontainer level classloader . So whenever this is reloaded The component gets reloaded. The only caveat is, this component cannot use core specific jars.

We will deprecate the runtimeLib = true/false option and the new options are

• runtimeLib=core : means this uses the runtimeLib of the collection
• runtimeLib= global : means this uses the runtimeLib of the corecontainer

example command to update global jar . This will lead to a reload of all components marked as runtimeLib=global

curl -X POST -H 'Content-type:application/json' --data-binary '
{
  "update-runtimelib": {
      "name": "lib-name" ,
      "url" : "http://host:port/url/of/jar",
      "sha512":"<the-new-sha512>"
  }
}' http://localhost:8983/api/cluster

Issue Links

• is related to: SOLR-13565 Node level runtime libs loaded from remote urls
• relates to: SOLR-13564 Runtime libs loaded from remote URLs should be available to all components
• links to: GitHub Pull Request #801