I have 25+ Elasticsearch cluster nodes where I have configured ingestion, data, and master nodes. Any changes to the Elasticsearch configuration need to be updated on each cluster node individually. For instance, if I need to modify an LDAP filter parameter, I must perform this update on every cluster node and restart the nodes in rolling order. If the change doesn't work and I need to update something again, I must repeat the process for every cluster node. This process is a bit hectic and time-consuming. Is there a better way to do this?
Is there a need to have the same configuration in each node since you already have nodes with specific functions?
For example, I have a 20 nodes cluster with master dedicated, hot tier and warm tier.
My hot tier is composed of 4 nodes, and only these for nodes have the auth configuration for ldap, the others will only authenticate internal users.
How is your cluster organized? If you have Kibana, which nodes are configured in Kibana, all 25+? When you send data, to which nodes you send it, all 25+ or just the ingestion layer?
1 Like
Hi @leandrojmp ,
Thank you for the reply.
I have the same configuration across all the cluster nodes. I believe that even though each node has its own specific function defined, we need to configure the same LDAP parameters on all the nodes. Cluster nodes should have identical configurations since requests can go to any node. That's what I gathered from some of the documentation. Please correct me if I'm wrong.
Actually, I have 3 ingestion nodes, 5 master nodes, and the remaining are data nodes with a hot tier. Could you let me know how I can configure my cluster so that I don't have to make changes to every node?