Hi everyone - I have a deployment related question. We are planning a
deployment model wherein the number of data nodes in an elastic search
cluster can be reduced or increased based on the projected load in a given
season. Given that we use unicast for node discovery, we need to maintain a
right list of nodes in the config file. I understand that one doesn't need
to have ALL the nodes listed but we are hoping that we list the nodes as
accurately as we possibly can.
Question I have is: Does elastic search deployment support a deployment
wherein the list of (unicast) nodes in the cluster can be pulled from a
centralized service?
Hi everyone - I have a deployment related question. We are planning a deployment model wherein the number of data nodes in an Elasticsearch cluster can be reduced or increased based on the projected load in a given season. Given that we use unicast for node discovery, we need to maintain a right list of nodes in the config file. I understand that one doesn't need to have ALL the nodes listed but we are hoping that we list the nodes as accurately as we possibly can.
Question I have is: Does Elasticsearch deployment support a deployment wherein the list of (unicast) nodes in the cluster can be pulled from a centralized service?
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.