I think this question is more aimed at design and performance of large number of cores. Also solr is designed to handle multiple cores effectively, however it would be interesting to know If you have observed any performance problem with growing number of cores, with number of nodes and solr version.
Regards Harshvardhan Ojha On Tue, Aug 12, 2014 at 12:33 PM, Anshum Gupta <ans...@anshumgupta.net> wrote: > Hi Ramprasad, > > You can certainly have a system with hundreds of cores. I know of more than > a few people who have done that successfully in their setups. > > At the same time, I'd also recommend to you to have a look at SolrCloud. > SolrCloud takes away the operational pains like replication/recovery etc. > to a major extent. I don't know about your security requirements and hard > bounds on that front but look at routing in SolrCloud to also figure out > multi-tenancy implementation here: > * SolrCloud Document Routing by Joel: > http://searchhub.org/2013/06/13/solr-cloud-document-routing/ > * Multi-level composite-id routing in SolrCloud: > http://searchhub.org/2014/01/06/10590/ > > > > On Mon, Aug 11, 2014 at 11:40 PM, Ramprasad Padmanabhan < > ramprasad...@gmail.com> wrote: > > > I need to store in SOLR all data of my clients mailing activitiy > > > > The data contains meta data like From;To:Date;Time:Subject etc > > > > I would easily have 1000 Million records every 2 months. > > > > What I am currently doing is creating cores per client. So I have 400 > cores > > already. > > > > Is this a good idea to do ? > > > > What is the general practice for creating cores > > > > > > -- > > Anshum Gupta > http://www.anshumgupta.net >
