Hi List,
I am trying to bring up a prototype cluster using ES5Alpha5. The node config in config/elasticsearch.yml is (pretty much ported from my prod ES2 config except where I was asked to remove stuff when ES5 was coming up):
cluster.name: <name>
node.name: bxb-sln-vm140
path.data: /home/xxx/elastic-data
path.logs: /home/xxx/elastic-logs
node.data: true
node.master: true
http.enabled: true
discovery.zen.ping.unicast.hosts: ["10.86.207.26:9300", "10.86.206.22:9300", "10.86.196.235:9300"]
discovery.zen.minimum_master_nodes: 2
discovery.zen.fd.ping_timeout: 30s
This is the output I am seeing on the logs:
[2016-09-15 11:00:13,854][INFO ][transport ] [bxb-sln-vm140] publish_address {127.0.0.1:9300}, bound_addresses {[::1]:9300}, {127.0.0.1:9300}
[2016-09-15 11:00:43,880][WARN ][node ] [bxb-sln-vm140] timed out while waiting for initial discovery state - timeout: 30s
[2016-09-15 11:00:43,895][INFO ][http ] [bxb-sln-vm140] publish_address {127.0.0.1:9200}, bound_addresses {[::1]:9200}, {127.0.0.1:9200}
[2016-09-15 11:00:43,895][INFO ][node ] [bxb-sln-vm140] started
This is the other output I see:
curl -XGET 'http://localhost:9200/_cluster/health?pretty=true'
{
"error" : {
"root_cause" : [
{
"type" : "master_not_discovered_exception",
"reason" : null
}
],
"type" : "master_not_discovered_exception",
"reason" : null
},
"status" : 503
}
Other FYI: I am kind of trying to move over my existing prod cluster to ES5 once its out of Alpha/Beta, is there any place that tracks all points to keep in mind when making the move? I already saw that I cannot specify shards and replicas on the .yml but instead through a POST (like!)
Thanks