Hi, The architecture is probably better served depending on the content and data sources.
If you have multiple data sources for each of the sites.. e.g database serving up site content, Feeds serving up syndicated content , then multicore will be better served using each core by data source core1-> database core2 -> RSS As with multiple sites, you can run multiple solr indexes with each index serving a website, Alternatively if you have common content across the sites, then you could use one of the cores to serve common content with other cores service site specific content. Hope this info helps. Regards, Ravi ________________________________ From: Otis Gospodnetic <otis_gospodne...@yahoo.com> To: solr-user@lucene.apache.org Sent: Thu, July 15, 2010 4:56:24 AM Subject: Re: Multiple cores or not? Hello there, I'm guessing the sites will be searched separately. In that case I'd recommend a core for each site. Otis ---- Sematext :: http://sematext.com/ :: Solr - Lucene - Nutch Lucene ecosystem search :: http://search-lucene.com/ ----- Original Message ---- > From: "scr...@asia.com" <scr...@asia.com> > To: solr-user@lucene.apache.org > Sent: Wed, July 14, 2010 3:02:36 PM > Subject: Multiple cores or not? > > > > > Hi, > > We are planning to host on same server different website that will use solr. > > What will be the best? > > One core with a field i schema: site1, site2 etc... and then add this in > every > >query > > Or one core per site? > > Thanks for your help > > > >
