Hi folks,

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.

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.

Further aspects such as monitoring become easier as well. We will need to
watch and tune the caches for the different pattern of hits that we see.

Is there anything else to evaluate before we move to a single core per type
setup?

We are using 4.4.0 currently and will be moving to latest 4.10.1 as a part
of the redesign as well.

Regards
Manoj

Reply via email to