This is a common approach to this problem, having separate cores keeps the apps from influencing each other when it comes to term frequencies & etc. It also keeps the chances of returning the wrong data do a minimum.
As to how many cores can fit, "it depends" (tm). There's lots of work going on right now, see: http://wiki.apache.org/solr/LotsOfCores. But having all those cores does allow you to expand your system pretty easily if you do run over the limit your hardware can handle, just move the entire core to a new machine. Only testing will tell you where that limit is. Best Erick On Wed, Jan 2, 2013 at 7:18 AM, Parvin Gasimzade <parvin.gasimz...@gmail.com > wrote: > Hi all, > > We have a system that enables users to create applications and store data > on their application. We want to separate the index of each application. We > create a core for each application and search on the given application when > user make query. Since there isn't any relation between the applications, > this solution could perform better than the storing all index together. > > I have two questions related to this. > 1. Is this a good solution? If not could you please suggest any better > solution? > 2. Is there a limit on the number of core that I can create on Solr? There > will be thousands maybe more application on the system. > > P.S. This question is also asked in the > stackoverflow< > http://stackoverflow.com/questions/14121624/max-number-of-core-in-solr-multi-core > > > . > > Thanks, > Parvin >
