Hi all,

Question in brief: in Solrcloud, how can we assign specific nodes to serve
a collection, given that our cloud is deployed using the backup/restore
feature?

We are using Solrcloud 8.5.2 with 5 nodes, serving 13 collections. The
majority of these collections are not large, but one of them is large and
is the most important one in our application. This important collection has
5 shards about 60 GB in size (more than double the largest other
collection) with about 330 M documents. Our nodes have 32 GB RAM and 8
CPUs. We use NFS, but when we go into production, we will have dedicated
SSDs available to us.

Since our most important collection is being used by users much more than
the other collections, we think it makes sense to serve its data from
specific nodes, which are not used to serve any other collection. So far,
we have not needed to do this, but we do now as we're seeing some
performance issues ...

The caveat is that we utilise the backup/restore feature of Solrcloud to
deploy our application on different data-centres.

We've read briefly about the Autoscaling features of Solrcloud, but have
not yet made use of them. However, I can't see whether Autoscaling allows
us to dedicate specific nodes to a collection.

Does anyone with any experience with this have any advice for us?

Kind regards,

Edd
--------------------
Edward Turner

Reply via email to