# 1. You want this node to never become a master node, only to hold data.
# This will be the "workhorse" of your cluster.
#
-#node.master: false
-#node.data: true
+# node.master: false
+# node.data: true
#
# 2. You want this node to only serve as a master: to not store any data and
# to have free resources. This will be the "coordinator" of your cluster.
# By default, multiple nodes are allowed to start from the same installation location
# to disable it, set the following:
-#node.max_local_storage_nodes: 1
+# node.max_local_storage_nodes: 1
#################################### Index ####################################
# and master node is elected. Multicast discovery is the default.
# Set to ensure a node sees N other master eligible nodes to be considered
-# operational within the cluster. This should be set to a quorum/majority of
+# operational within the cluster. This should be set to a quorum/majority of
# the master-eligible nodes in the cluster.
#
-#discovery.zen.minimum_master_nodes: 1
+# discovery.zen.minimum_master_nodes: 0
# Set the time to wait for ping responses from other nodes when discovering.
# Set this option to a higher value on a slow or congested network
#
# 1. Disable multicast discovery (enabled by default):
#
-discovery.zen.ping.multicast.enabled: false
+# discovery.zen.ping.multicast.enabled: false
#
# 2. Configure an initial list of master nodes in the cluster
# to perform discovery when new nodes (master or data) are started:
#
-#discovery.zen.ping.unicast.hosts: ["host1", "host2:port"]
+# discovery.zen.ping.unicast.hosts: ["0.0.0.0",]
# EC2 discovery allows to use AWS EC2 API in order to perform discovery.
#
# it unless you need it is recommended (it is disabled by default).
#
#http.jsonp.enable: true
-