Managing an OpenSearch cluster can be a complex and time-consuming task, particularly when it comes to scaling and resizing resources on the production cluster. This is where OMC comes in, providing a streamlined and automated way to manage OpenSearch resources.
One of the key features of OMC is its quick actions feature, which allows users to quickly and easily scale their OpenSearch clusters up or down, resize resources, such as CPU and memory, and resize disks.
The quick actions button can be found on every node group, singed with 3 dots, for example:
Now, let’s take a closer look at each of these quick actions and their benefits.
Scale down nodes
Check out this video for instructions on how to scale down nodes.
Scale Up Replicas
When scaling up replicas, users can quickly add nodes to a cluster, allowing them to handle increasing workloads and data volumes. Using OMC quick actions, users can seamlessly and efficiently increase the size of their OpenSearch cluster without having to manually update cluster configurations. This saves a significant amount of time and effort.
Scale Down Replicas
When scaling down replicas, it’s essential to ensure that any data on the nodes being removed is safely transferred to other nodes in the cluster. This is especially important when scaling down nodes with a data role, since these nodes could contain critical data that must be preserved. This is addressed by a feature that allows users to safely drain data nodes before scaling down data role nodes. By setting the ‘drainDataNodes’ key to true, The OMC transfers any data on the nodes being removed to other nodes in the cluster first. This ensures that users can scale down their OpenSearch cluster without risking data loss or corruption.
Resizing resources, such as CPU and memory allows users to adjust the amount of processing power and memory available to OpenSearch clusters. This can be particularly useful when dealing with performance issues, since it allows users to allocate more resources to their cluster, as needed. Additionally, resizing resources helps save money, allowing users to allocate resources more efficiently.
However, it’s important to be aware that this operation triggers a rolling restart of the node pool. A rolling restart is a common Kubernetes strategy that updates or modifies clusters, which involves taking down and restarting nodes one at a time, in a controlled manner. While the rolling restart can cause temporary downtime in some nodes, the automatic and controlled nature of the process ensures that the cluster remains stable and reliable, allowing users to work with confidence.
Resizing disks allows users to increase the amount of storage available in their OpenSearch cluster. This is particularly useful when dealing with growing data volumes, allowing users to add more storage space as needed. By using OMC quick actions, users can easily resize disks without having to manually update their cluster configurations.