Before you dig into the details of this technical guide, have you tried asking OpsGPT?
You'll receive concise answers that will help streamline your Elasticsearch/OpenSearch operations.
Try OpsGPT now for step-by-step guidance and tailored insights into your Elasticsearch/ OpenSearch operation.
Before you dig into the details of this guide, have you tried asking OpsGPT? You’ll receive concise answers that will help streamline your Elasticsearch/OpenSearch operations.
Try OpsGPT now for step-by-step guidance and tailored insights into your search operation.
To easily resolve issues in your deployment, try AutoOps for Elasticsearch. It diagnoses problems by analyzing hundreds of metrics collected by a lightweight agent and offers guidance for resolving them.
What does this mean?
Ideally, Elasticsearch clusters should have three dedicated master nodes and no other nodes with master roles. If you have other nodes carrying master roles, they should be reconfigured.
This issue is monitored by Opster AutoOps in real-time with personalized recommendations provided for your own system. You can also configure notifications to avoid this issue forming in the future.
Why does this occur?
The cluster’s configuration is not optimal if you have nodes carrying master roles that are not one of the 3 dedicated master nodes. Having dedicated master nodes is crucial for the stability and performance of the Elasticsearch cluster. If other nodes also carry the master role, it can lead to potential issues and inefficiencies.
Possible impact and consequences of
The possible impact of this includes:
- Performance degradation: Nodes with multiple roles can become resource-constrained, leading to slower response times and reduced throughput.
- Increased risk of cluster instability: If a node with a master role fails, it can cause disruptions in the cluster’s operation.
- Difficulty in troubleshooting: Having multiple nodes with master roles can make it challenging to identify the root cause of issues in the cluster.
How to resolve
To achieve the optimal master node configuration, follow these steps according to your needs:
1. Add more dedicated master nodes: It is recommended to add as many dedicated master nodes, so that in total there are three dedicated master nodes. To add a dedicated master node, update the `elasticsearch.yml` configuration file on the new node with the following settings:
node.master: true node.data: false node.ingest: false
Then, restart the Elasticsearch service on the new node.
2. Remove the master role from all other nodes that are not dedicated master nodes: Update the `elasticsearch.yml` configuration file on each of these nodes with the following settings:
node.master: false
Restart the Elasticsearch service on each of these nodes after updating the configuration.
3. Monitor the cluster health and performance: After making the changes, monitor the cluster’s health using the `_cluster/health` API endpoint and check for improvements in performance and stability. If you are using Opster AutoOps, you can simply turn to the Cluster View dashboard to see the new events related to cluster health.
GET /_cluster/health
Conclusion
By following these steps, you can resolve the “Move to dedicated master nodes” issue and improve the stability and performance of your Elasticsearch cluster.
