When peer nodes are not correct or dead, ES spends 30s doing nothing,
what property configures it?
None of these work:
Builder builder = ImmutableSettings.settingsBuilder()
.put(ES_CONFIG_CLUSTER_PROPERTY_KEY, this.clusterName)
.putArray(ES_CONFIG_PEER_HOSTS_PROPERTY_KEY,
this.peerHosts)
.put("discovery.zen.fd.ping_timeout", 2)
.put("discovery.zen.ping.timeout", 2)
.put("discovery.zen.ping.multicast.enabled", false)
.put("gateway.expected_nodes", 2);
The node will wait for a proper discovery to happen (finding a master node) on startup, by default, it is 30 seconds. You can configure that by setting discovery.initial_state_timeout setting.
On Thursday, February 9, 2012 at 6:53 PM, Bozena Wegorek wrote:
When peer nodes are not correct or dead, ES spends 30s doing nothing,
what property configures it?
None of these work:
Builder builder = ImmutableSettings.settingsBuilder()
.put(ES_CONFIG_CLUSTER_PROPERTY_KEY, this.clusterName)
.putArray(ES_CONFIG_PEER_HOSTS_PROPERTY_KEY,
this.peerHosts)
.put("discovery.zen.fd.ping_timeout", 2)
.put("discovery.zen.ping.timeout", 2)
.put("discovery.zen.ping.multicast.enabled", false)
.put("gateway.expected_nodes", 2);
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.