Dear Solr Members, We are using SolrCloud as the search provider of a multi-tenant cloud based application. We have one schema for all the tenants. The indexes will have large number(millions) of documents.
As of our research, we have two options, - One large collection for all the tenants and use Composite-ID routing - Collection per tenant The below mail says, https://mail-archives.apache.org/mod_mbox/lucene-solr-user/201403.mbox/%3c5324cd4b.2020...@protulae.com%3E SolrCloud is *more scalable in terms of index size*. Plus you get redundancy which can't be underestimated in a hosted solution. AND The issue is management. 1000s of cores/collections require a level of automation. On the other hand, having a single core/collection means if you make one change to the schema or solrconfig, it affects everyone. Based on the above facts we think One large collection will be the way to go. Questions: 1. Is that the right way to go? 2. Will it be a hassle when we need to do reindexing? 3. What is the chance of entire collection crash? (in that case all tenants will be affected and reindexing will be painful. Thank you in advance for your kind opinion. Best Regards, Chamil -- http://kavimalla.blgospot.com http://kdchamil.blogspot.com
