On Tue, 2014-10-07 at 14:27 +0200, Manoj Bharadwaj wrote: > My team inherited a SOLR setup with an architecture that has a core for > every customer. We have a few different types of cores, say "A", "B", C", > and for each one of this there is a core per customer - namely "A1", > "A2"..., "B1", "B2"... Overall we have over 600 cores. We don't know the > history behind the current design - the exact reasons why it was done the > way it was done - one probable consideration was to ensure a customer data > separate from other.
It is not a bad reason. It ensures that ranked search is optimized towards each customer's data and makes it easy to manage adding and removing customers. > We want to go to a single core per type architecture, and move on to SOLR > cloud as well in near future to achieve sharding via the features cloud > provides. If the setup is heavy queried on most of the cores or is there are core-spanning searches, collapsing the user-specific cores into fewer super-cores might lower hardware requirements a bit. On the other hand, it most of the cores are idle most of the time, the 1 core/customer setup would be give better utilization of the hardware. Why do you want to collapse the cores? - Toke Eskildsen, State and University Library, Denmark
