Hello, We are using ES with the azure cloud plugin for node communication. Our current set-up is : 2 data node (hosted on azure ubuntu 14.04 VM) 3.5 giga RAM, 2 Cores (AKA medium VM) ES version 1.0.0.0. 5 shards and 2 replicas. The storing and query are done by Kibana and logstash which are hosted on separate machines. Logstash connects to the cluster via the node protocol. The problem we are having is that for some unknown reason one of the data nodes leaves the cluster, no errors are reported in the log of the machine that left and the node keeps running independently (wired, I know) when restarting the elasticsearch service on the lonely node it rejoins the cluster. After the node rejoins the cluster everything seems ok until it or the other data node will leave the cluster again (Meaning that there is no specific node that have the problem, each one of the nodes can suddenly leave the cluster). Did anyone encounter this problem using the azure plugin for node discovery? Any input on how to approach this issue? Thanks Neta.
-- View this message in context: http://elasticsearch-users.115913.n3.nabble.com/Elasticsearch-with-azure-cloud-plugin-tp4059340.html Sent from the ElasticSearch Users mailing list archive at Nabble.com. -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/1404718530391-4059340.post%40n3.nabble.com. For more options, visit https://groups.google.com/d/optout.
