Re: Double Solr Installation on Single Tomcat (or Double Index)
Tom Weber napisał(a):
Hello,
I need to have a second separate index (separate data) on the same
server.
Is there a possibility to do this in a single solr install on a
tomcat server or do I need to have a second instance in the same
tomcat install ?
You will need separate instances within the same Tomcat.
If either one is possible, does somebody has some advice how to set
this up, and how to be sure that both indexes do not interact ?
Create context xml file for each SOLR application in the folder :
CATALINA_HOME\conf\Catalina\localhost\context_name.xml.
crossContext="true">
value="${catalina.home}\solr_data_files\" override="true" />
Adjust docBase to point at solr.war.
Adjust solr/home to point at solr_data_files - different folders for
different SOLR instances.
If the context xml file name is called solr1.xml then you can acces that
solr instance using following url http://host:port/solr1/admin.
Many thanks for any help,
Best Greetings,
Tom
--
200 zlotych bonusu w eliminacjach do Mistrzostw Europy dla Ciebie!
BETWAY.com >>> http://link.interia.pl/f199f
SolrCore as Singleton?
Is there a good reason for implementing SolrCore as a Singleton? We are experimenting with running Solr as a Spring service embedded in our app. Since it is a Singleton we cannot have more than one index (not currently a problem, but could be). I note the comment: // Singleton for now... If there is no specific reason for making it a Singleton, I'd vote for removing this so that the SolrCore(dataDir, schema) constructor could be used to instantiate multiple cores. Seems to me that since the primary usage scenario of solr is access via REST (i.e. no Solr jar/API), the Singleton pattern is not necessary here. --Joachim
Re: SolrCore as Singleton?
If there is no specific reason for making it a Singleton, I'd vote for removing this so that the SolrCore(dataDir, schema) constructor could be used to instantiate multiple cores. I agree with your arguments. However (although being new to Solr) there is more than one way to do it, I think. To be more specific it seems that using several different indexes with individual datadirs and schemas is very useful, based on my impression that many enterprise users seem to want this functionality. It is not difficult to imagine such a usage pattern or implementation, in its abstract sense, of Solr for almost all uses. However (and this is where most you guys should fill me in), it could be wasteful to run multiple complete instances. Could information be shared in some way between the instances to save on resources? Perhaps what I am really trying to say here, is that we have to look at the whole model when considering how to implement better support for the desired usage pattern outlined above. Eivind
Re: SolrCore as Singleton?
: Is there a good reason for implementing SolrCore as a Singleton? I'm going to sidestep the issue of wether there *was* a good reason for it, as well as the "does the singleton pattern make sense for the current usage" question and answer what i think is an equally significant question: "what are the implications of trying to change it now?" ... the biggest i can think of being that SolrConfig is also a static singleton, and a *lot* of code in the Solr code base would need to be changed to support multiple SolrConfigs ... and without multiple SolrConfigs, there really isnt' any reason to have multiple SolrCores. -Hoss
Re: SolrCore as Singleton?
Chris Hostetter wrote: I'm going to sidestep the issue of wether there *was* a good reason for it, as well as the "does the singleton pattern make sense for the current usage" question and answer what i think is an equally significant question: "what are the implications of trying to change it now?" ... the biggest i can think of being that SolrConfig is also a static singleton, and a *lot* of code in the Solr code base would need to be changed to support multiple SolrConfigs ... and without multiple SolrConfigs, there really isnt' any reason to have multiple SolrCores. This actually underlines that my guess was right to a certain extent. Changing from singleton is not straightforward. I am currently in the startup phase of my thesis regarding open source and enterprise search. After having worked at perhaps the leading major enterprise search company, I have the impression that multiple collections is a very common feature (and very sought-after). It is a trend I see not just directly from my work, but most certainly also as a result of enterprise search solutions becoming more common in general. However I must say that Solr seems to be approaching the problem from a very logical angle. What really is missing is a more abstract layer, call it application framework, that probably will come afterwards anyway. This will perhaps evolve naturally as part of the Solr project at a later stage, or perhaps even as a separate open source project building on Solr. Until this framework is available with its appropriate configuration files, administrator interface and so on in place, it seems a bit unnatural to support multiple collections from the same application instance. Bottom line (for now): I think that users looking for enterprise search solutions must have a simple way of creating multiple collections from within the same application. I apologize for my very philosophical e-mail, but I tend to become somewhat visionary and conceptual after a few beers, and this might not be the perfect forum for these discussions(?) :) Eivind
Re: SolrCore as Singleton?
: I am currently in the startup phase of my thesis regarding open source : and enterprise search. After having worked at perhaps the leading major : enterprise search company, I have the impression that multiple : collections is a very common feature (and very sought-after). It is a : trend I see not just directly from my work, but most certainly also as a : result of enterprise search solutions becoming more common in general. SolrCore being a singleton doesn't prevent you from having multiple collections per JVM -- you just need to run multiple instances of the webapp within a single servlet container using JNDI to specify the seperate solr.home directories, specifics for doing this in Tomcat are on the wiki... http://wiki.apache.org/solr/SolrTomcat : Until this framework is available with its appropriate configuration : files, administrator interface and so on in place, it seems a bit : unnatural to support multiple collections from the same application : instance. : : Bottom line (for now): I think that users looking for enterprise search : solutions must have a simple way of creating multiple collections from : within the same application. Well it's pretty easy right now to make a new collection -- it's just two new files (solrconfig.xml and schema.xml) -Hoss
Re: SolrCore as Singleton?
Nice. Is the same doable under Jetty? (never had to deal with JNDI under Jetty) Otis - Original Message From: Chris Hostetter <[EMAIL PROTECTED]> To: solr-user@lucene.apache.org Sent: Friday, September 8, 2006 1:46:19 AM Subject: Re: SolrCore as Singleton? : I am currently in the startup phase of my thesis regarding open source : and enterprise search. After having worked at perhaps the leading major : enterprise search company, I have the impression that multiple : collections is a very common feature (and very sought-after). It is a : trend I see not just directly from my work, but most certainly also as a : result of enterprise search solutions becoming more common in general. SolrCore being a singleton doesn't prevent you from having multiple collections per JVM -- you just need to run multiple instances of the webapp within a single servlet container using JNDI to specify the seperate solr.home directories, specifics for doing this in Tomcat are on the wiki... http://wiki.apache.org/solr/SolrTomcat : Until this framework is available with its appropriate configuration : files, administrator interface and so on in place, it seems a bit : unnatural to support multiple collections from the same application : instance. : : Bottom line (for now): I think that users looking for enterprise search : solutions must have a simple way of creating multiple collections from : within the same application. Well it's pretty easy right now to make a new collection -- it's just two new files (solrconfig.xml and schema.xml) -Hoss
Re: SolrCore as Singleton?
: Nice. Is the same doable under Jetty? (never had to deal with JNDI : under Jetty) i haven't tried it personally, but according to Yoav "reading" JNDI options is part of hte Servlet Spec, and billa found a refrene to useing "" to do so... http://www.nabble.com/Re%3A-multiple-solr-webapps-p3991310.html ...where exactly that option goes in Jetty's configuration isn't something i'm clear on. : - Original Message : From: Chris Hostetter <[EMAIL PROTECTED]> : To: solr-user@lucene.apache.org : Sent: Friday, September 8, 2006 1:46:19 AM : Subject: Re: SolrCore as Singleton? : : : : I am currently in the startup phase of my thesis regarding open source : : and enterprise search. After having worked at perhaps the leading major : : enterprise search company, I have the impression that multiple : : collections is a very common feature (and very sought-after). It is a : : trend I see not just directly from my work, but most certainly also as a : : result of enterprise search solutions becoming more common in general. : : SolrCore being a singleton doesn't prevent you from having multiple : collections per JVM -- you just need to run multiple instances of the : webapp within a single servlet container using JNDI to specify the : seperate solr.home directories, specifics for doing this in Tomcat are on : the wiki... :http://wiki.apache.org/solr/SolrTomcat : : : Until this framework is available with its appropriate configuration : : files, administrator interface and so on in place, it seems a bit : : unnatural to support multiple collections from the same application : : instance. : : : : Bottom line (for now): I think that users looking for enterprise search : : solutions must have a simple way of creating multiple collections from : : within the same application. : : Well it's pretty easy right now to make a new collection -- it's : just two new files (solrconfig.xml and schema.xml) : : : : : -Hoss : : : : -Hoss
