Scale a Solr Cluster Manually

Scale Solr nodes in Managed Search clusters to meet the search needs of your organization. You can specify these scale-related attributes of a cluster when you create it, and when you manually scale the cluster later.

Attribute Description

nodeType

Solr node type. Different Solr node types make available different numbers of CPUs and different amounts of memory. Different node types also have different default amounts of disk storage, if you create a cluster without specifying storageSizeGB.

nodeCount

Number of Solr nodes. This top-level nodeCount serves two purposes. First, with manual scaling, it is a number you set when creating a cluster and that you can change. It is also the current node count.

Note
By default, Managed Search supports clusters of between 3 and 30 nodes. If you need more nodes, Contact Customer Support.

storageSizeGB

Amount of disk space to use per Solr node, in gigabytes.

Important
You can’t decrease storageSizeGB; you can only increase it.

Note
During both manual scaling and autoscaling, Managed Search ensures that no data is lost.

Additionally, you can enable autoscaling to ensure that the performance of Solr nodes in your Managed Search clusters scales up and down automatically to meet varying levels of demand.

Node type (nodeType) and storage size (storageSizeGB) settings apply both when autoscaling is enabled and disabled.

Example JSON request body

Use this JSON request body in a POST request to the /customers/customerId/clusters endpoint (to create a cluster) or in a PUT or PATCH request to the /customers/customerId/clusters/clusterId endpoint (to modify a cluster). The request sets the Solr node count to use when autoscaling isn’t enabled to 5.

{
  "id": "test-1",
  "nodeCount": 5,
  "nodeType": "standard-2",
  "storageSizeGB": 20,
  "description": "test cluster",
  "maintenanceWindow": "SUNDAY,21:45"
}