You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Noble Paul (JIRA)" <ji...@apache.org> on 2014/10/30 18:30:34 UTC
[jira] [Created] (SOLR-6681) remove configurations from
solrconfig.xml and eliminate per core class loading
Noble Paul created SOLR-6681:
--------------------------------
Summary: remove <lib> configurations from solrconfig.xml and eliminate per core class loading
Key: SOLR-6681
URL: https://issues.apache.org/jira/browse/SOLR-6681
Project: Solr
Issue Type: Improvement
Reporter: Noble Paul
As Solr moves more towards cloud ,solrconfig is stored in Zookeeper. Storing the local library information in a file stored in a remote and common location for all nodes make no sense.
In this new world, cores are created and managed by the solrcloud system and there is no need to have separate classloading for each core and a lot of unnecessary classloading issues in solr can go away
Going forward, all cores in a node will have only one classpath. We may define a standard directory such as 'ext' under the HOME and let users store all their jars there
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org