# Azure Cloud Plugin Problems

**URL:** <https://discuss.elastic.co/t/azure-cloud-plugin-problems/15600>\
**Category:** Elasticsearch\
**Created:** [February 4, 2014, 9:42pm UTC](https://discuss.elastic.co/t/azure-cloud-plugin-problems/15600 "2014-02-04T21:42:56Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Andrew\_Westgarth](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/andrew_westgarth/32/1823_2.png) [@Andrew\_Westgarth](https://discuss.elastic.co/u/Andrew_Westgarth)\
**Post date:** [February 4, 2014, 9:42pm UTC](https://discuss.elastic.co/t/azure-cloud-plugin-problems/15600/1 "2014-02-04T21:42:56Z")

</div>

Hi,  
I read with interest the news about the Azure Cloud Plugin over the  
weekend and today have been trying to get it working with Windows VMs on  
Azure with mixed levels of success.

I have two environments/clusters one which has been running for a few weeks  
and another which is brand new and only been running for a couple of days;  
both have the head plugin installed so I can see the status of the  
cluster(s).

All of the clusters consist of 3 machines are using the Windows Server 2012  
R2 Datacenter base image with java 7 added, and elasticsearch 0.90.10  
installed as a service set to automatic startup.

Cluster 1 - been running using multicast discovery disabled and the ip  
addresses of the nodes listed. I have since installed the azure cloud  
plugin, added the certificate and configuration to the node and enabled  
multicast discovery again and commented out the list of ip addresses. Now  
when I view the details of the cluster, none of the nodes can see each  
other and the cluster health status is marked in amber as the full cluster  
is no longer available.

the elasticsearch.yml file is as follows:

##################### Elasticsearch Configuration Example  
#####################

# This file contains an overview of various configuration settings,

# targeted at operations staff. Application developers should

# consult the guide at [http://elasticsearch.org/guide](http://elasticsearch.org/guide).

# 

# The installation procedure is covered at

# \<

> **[Elastic — The Search AI Company](https://www.elastic.co)**
>
> Power insights and outcomes with The Elastic Search AI Platform. See into your data and find answers that matter with enterprise solutions designed to help you accelerate time to insight. Try Elastic ...

> .

# 

# Elasticsearch comes with reasonable defaults for most settings,

# so you can try it out without bothering with configuration.

# 

# Most of the time, these defaults are just fine for running a production

# cluster. If you're fine-tuning your cluster, or wondering about the

# effect of certain configuration option, please _do ask_ on the

# mailing list or IRC channel [[Elastic — The Search AI Company | Elastic](http://elasticsearch.org/community)].

# Any element in the configuration can be replaced with environment

variables

# by placing them in ${...} notation. For example:

# 

# node.rack: ${RACK\_ENV\_VAR}

# For information on supported formats and syntax for the config file, see

# \<

> **[Elastic — The Search AI Company](https://www.elastic.co)**
>
> Power insights and outcomes with The Elastic Search AI Platform. See into your data and find answers that matter with enterprise solutions designed to help you accelerate time to insight. Try Elastic ...

> 

################################### Cluster  
###################################

# Cluster name identifies your cluster for auto-discovery. If you're running

# multiple clusters on the same network, make sure you're using unique

names.

# 

cluster.name: elasticsearch

#################################### Node  
#####################################

# Node names are generated dynamically on startup, so you're relieved

# from configuring them manually. You can tie this node to a specific name:

# 

# node.name: "Franz Kafka"

# Every node can be configured to allow or deny being eligible as the

master,

# and to allow or deny to store the data.

# 

# Allow this node to be eligible as a master node (enabled by default):

# 

# node.master: true

# 

# Allow this node to store data (enabled by default):

# 

# node.data: true

# You can exploit these settings to design advanced cluster topologies.

# 

# 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

# 

# 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.

# 

# node.master: true

# node.data: false

# 

# 3. You want this node to be neither master nor data node, but

# to act as a "search load balancer" (fetching data from nodes,

# aggregating results, etc.)

# 

# node.master: false

# node.data: false

# Use the Cluster Health API [[http://localhost:9200/\_cluster/health](http://localhost:9200/_cluster/health)], the

# Node Info API [[http://localhost:9200/\_cluster/nodes](http://localhost:9200/_cluster/nodes)] or GUI tools

# such as [http://github.com/lukas-vlcek/bigdesk](http://github.com/lukas-vlcek/bigdesk) and

# [http://mobz.github.com/elasticsearch-head](http://mobz.github.com/elasticsearch-head) to inspect the cluster state.

# A node can have generic attributes associated with it, which can later be

used

# for customized shard allocation filtering, or allocation awareness. An

attribute

# is a simple key value pair, similar to node.key: value, here is an

example:

# 

# node.rack: rack314

# 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

#################################### Index  
####################################

# You can set a number of options (such as shard/replica options, mapping

# or analyzer definitions, translog settings, ...) for indices globally,

# in this file.

# 

# Note, that it makes more sense to configure index settings specifically

for

# a certain index, either when creating it or by using the index templates

API.

# 

# See \<

[Elastic — The Search AI Company | Elastic](http://elasticsearch.org/guide/en/elasticsearch/reference/current/index-modules.html)\>  
and

# \<

> **[Elastic — The Search AI Company](https://www.elastic.co)**
>
> Power insights and outcomes with The Elastic Search AI Platform. See into your data and find answers that matter with enterprise solutions designed to help you accelerate time to insight. Try Elastic ...

> 

# for more information.

# Set the number of shards (splits) of an index (5 by default):

# 

# index.number\_of\_shards: 5

# Set the number of replicas (additional copies) of an index (1 by default):

# 

# index.number\_of\_replicas: 1

# Note, that for development on a local machine, with small indices, it

usually

# makes sense to "disable" the distributed features:

# 

# index.number\_of\_shards: 1

# index.number\_of\_replicas: 0

# These settings directly affect the performance of index and search

operations

# in your cluster. Assuming you have enough machines to hold shards and

# replicas, the rule of thumb is:

# 

# 1. Having more _shards_ enhances the _indexing_ performance and allows to

# _distribute_ a big index across machines.

# 2. Having more _replicas_ enhances the _search_ performance and improves

the

# cluster _availability_.

# 

# The "number\_of\_shards" is a one-time setting for an index.

# 

# The "number\_of\_replicas" can be increased or decreased anytime,

# by using the Index Update Settings API.

# 

# Elasticsearch takes care about load balancing, relocating, gathering the

# results from nodes, etc. Experiment with different settings to fine-tune

# your setup.

# Use the Index Status API ([http://localhost:9200/A/\_status](http://localhost:9200/A/_status)) to inspect

# the index status.

#################################### Paths  
####################################

# Path to directory containing configuration (this file and logging.yml):

# 

# path.conf: /path/to/conf

# Path to directory where to store index data allocated for this node.

# 

# path.data: /path/to/data

# 

# Can optionally include more than one location, causing data to be striped

across

# the locations (a la RAID 0) on a file level, favouring locations with

most free

# space on creation. For example:

# 

# path.data: /path/to/data1,/path/to/data2

# Path to temporary files:

# 

# path.work: /path/to/work

# Path to log files:

# 

# path.logs: /path/to/logs

# Path to where plugins are installed:

# 

# path.plugins: /path/to/plugins

#################################### Plugin  
###################################

# If a plugin listed here is not installed for current node, the node will

not start.

# 

# plugin.mandatory: mapper-attachments,lang-groovy

################################### Memory  
####################################

# Elasticsearch performs poorly when JVM starts swapping: you should ensure

that

# it _never_ swaps.

# 

# Set this property to true to lock the memory:

# 

# bootstrap.mlockall: true

# Make sure that the ES\_MIN\_MEM and ES\_MAX\_MEM environment variables are set

# to the same value, and that the machine has enough memory to allocate

# for Elasticsearch, leaving enough memory for the operating system itself.

# 

# You should also make sure that the Elasticsearch process is allowed to

lock

# the memory, eg. by using `ulimit -l unlimited`.

############################## Network And HTTP  
###############################

# Elasticsearch, by default, binds itself to the 0.0.0.0 address, and

listens

# on port [9200-9300] for HTTP traffic and on port [9300-9400] for

node-to-node

# communication. (the range means that if the port is busy, it will

automatically

# try the next port).

# Set the bind address specifically (IPv4 or IPv6):

# 

# network.bind\_host: 192.168.0.1

# Set the address other nodes will use to communicate with this node. If not

# set, it is automatically derived. It must point to an actual IP address.

# 

# network.publish\_host: 192.168.0.1

# Set both 'bind\_host' and 'publish\_host':

# 

# network.host: 192.168.0.1

# Set a custom port for the node to node communication (9300 by default):

# 

# transport.tcp.port: 9300

# Enable compression for all communication between nodes (disabled by

default):

# 

# transport.tcp.compress: true

# Set a custom port to listen for HTTP traffic:

# 

# http.port: 9200

# Set a custom allowed content length:

# 

# http.max\_content\_length: 100mb

# Disable HTTP completely:

# 

# http.enabled: false

################################### Gateway  
###################################

# The gateway allows for persisting the cluster state between full cluster

# restarts. Every change to the state (such as adding an index) will be

stored

# in the gateway, and when the cluster starts up for the first time,

# it will read its state from the gateway.

# There are several types of gateway implementations. For more information,

see

# \<

> **[Elastic — The Search AI Company](https://www.elastic.co)**
>
> Power insights and outcomes with The Elastic Search AI Platform. See into your data and find answers that matter with enterprise solutions designed to help you accelerate time to insight. Try Elastic ...

> .

# The default gateway type is the "local" gateway (recommended):

# 

# gateway.type: local

# Settings below control how and when to start the initial recovery process

on

# a full cluster restart (to reuse as much local data as possible when

using shared

# gateway).

# Allow recovery process after N nodes in a cluster are up:

# 

# gateway.recover\_after\_nodes: 1

# Set the timeout to initiate the recovery process, once the N nodes

# from previous setting are up (accepts time value):

# 

# gateway.recover\_after\_time: 5m

# Set how many nodes are expected in this cluster. Once these N nodes

# are up (and recover\_after\_nodes is met), begin recovery process

immediately

# (without waiting for recover\_after\_time to expire):

# 

# gateway.expected\_nodes: 2

############################# Recovery Throttling  
#############################

# These settings allow to control the process of shards allocation between

# nodes during initial recovery, replica allocation, rebalancing,

# or when adding and removing nodes.

# Set the number of concurrent recoveries happening on a node:

# 

# 1. During the initial recovery

# 

# cluster.routing.allocation.node\_initial\_primaries\_recoveries: 4

# 

# 2. During adding/removing nodes, rebalancing, etc

# 

# cluster.routing.allocation.node\_concurrent\_recoveries: 2

# Set to throttle throughput when recovering (eg. 100mb, by default 20mb):

# 

# indices.recovery.max\_bytes\_per\_sec: 20mb

# Set to limit the number of open concurrent streams when

# recovering a shard from a peer:

# 

# indices.recovery.concurrent\_streams: 5

################################## Discovery  
##################################

# Discovery infrastructure ensures nodes can be found within a cluster

# 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. Its recommended to set it to a higher

value

# than 1 when running more than 2 nodes in the cluster.

# 

# discovery.zen.minimum\_master\_nodes: 1

# 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

# to minimize discovery failures:

# 

# discovery.zen.ping.timeout: 3s

# For more information, see

# \<

> **[Elastic — The Search AI Company](https://www.elastic.co)**
>
> Power insights and outcomes with The Elastic Search AI Platform. See into your data and find answers that matter with enterprise solutions designed to help you accelerate time to insight. Try Elastic ...

> 

# Unicast discovery allows to explicitly control which nodes will be used

# to discover the cluster. It can be used when multicast is not present,

# or to restrict the cluster communication-wise.

# 

# 1. Disable multicast discovery (enabled by default):

# 

# 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: ["10.0.0.4", "10.0.0.5", "10.0.0.6"]

# EC2 discovery allows to use AWS EC2 API in order to perform discovery.

# 

# You have to install the cloud-aws plugin for enabling the EC2 discovery.

# 

# For more information, see

# \<

> **[Elastic — The Search AI Company](https://www.elastic.co)**
>
> Power insights and outcomes with The Elastic Search AI Platform. See into your data and find answers that matter with enterprise solutions designed to help you accelerate time to insight. Try Elastic ...

> 

# 

# See [http://elasticsearch.org/tutorials/elasticsearch-on-ec2/](http://elasticsearch.org/tutorials/elasticsearch-on-ec2/)

# for a step-by-step tutorial.

################################## Slow Log  
##################################

# Shard level query and fetch threshold logging.

#index.search.slowlog.threshold.query.warn: 10s  
#index.search.slowlog.threshold.query.info: 5s  
#index.search.slowlog.threshold.query.debug: 2s  
#index.search.slowlog.threshold.query.trace: 500ms  
#index.search.slowlog.threshold.fetch.warn: 1s  
#index.search.slowlog.threshold.fetch.info: 800ms  
#index.search.slowlog.threshold.fetch.debug: 500ms  
#index.search.slowlog.threshold.fetch.trace: 200ms  
#index.indexing.slowlog.threshold.index.warn: 10s  
#index.indexing.slowlog.threshold.index.info: 5s  
#index.indexing.slowlog.threshold.index.debug: 2s  
#index.indexing.slowlog.threshold.index.trace: 500ms  
################################## GC Logging  
################################  
#monitor.jvm.gc.young.warn: 1000ms  
#monitor.jvm.gc.young.info: 700ms  
#monitor.jvm.gc.young.debug: 400ms  
#monitor.jvm.gc.old.warn: 10s  
#monitor.jvm.gc.old.info: 5s  
#monitor.jvm.gc.old.debug: 2s  
################################# AZURE PLUGIN  
###############################  
cloud:  
azure:  
keystore: c:/Certs/certificate.pfx  
password: password  
subscription\_id: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx  
service\_name: apw-es-vms  
discovery:  
type: azure

Cluster 2 - brand new clean cluster with same base configuration and only  
differences in elasticsearch.yml file are subscription id, service name and  
cluster name. Once again none of the nodes in this configuration can see  
each other.

I suspect this is a configuration issue but my experience with  
elasticsearch is limited. Does anyone have any ideas what I could have  
configured incorrectly?

Thanks

Andrew

--  
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 [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/12cca085-c7db-440e-8740-0bb973ff68a5%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/12cca085-c7db-440e-8740-0bb973ff68a5%40googlegroups.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [February 4, 2014, 10:22pm UTC](https://discuss.elastic.co/t/azure-cloud-plugin-problems/15600/2 "2014-02-04T22:22:49Z")

</div>

Could you please GIST your logs on both nodes?  
Also, could you change Log level to TRACE for discovery? (See config/logging.yml file)

Thanks

--  
David 😉  
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs

Le 4 févr. 2014 à 22:42, Andrew Westgarth [mail@hawaythelads.co.uk](mailto:mail@hawaythelads.co.uk) a écrit :

Hi,  
I read with interest the news about the Azure Cloud Plugin over the weekend and today have been trying to get it working with Windows VMs on Azure with mixed levels of success.

I have two environments/clusters one which has been running for a few weeks and another which is brand new and only been running for a couple of days; both have the head plugin installed so I can see the status of the cluster(s).

All of the clusters consist of 3 machines are using the Windows Server 2012 R2 Datacenter base image with java 7 added, and elasticsearch 0.90.10 installed as a service set to automatic startup.

Cluster 1 - been running using multicast discovery disabled and the ip addresses of the nodes listed. I have since installed the azure cloud plugin, added the certificate and configuration to the node and enabled multicast discovery again and commented out the list of ip addresses. Now when I view the details of the cluster, none of the nodes can see each other and the cluster health status is marked in amber as the full cluster is no longer available.

the elasticsearch.yml file is as follows:

##################### ElasticSearch Configuration Example #####################

# This file contains an overview of various configuration settings,

# targeted at operations staff. Application developers should

# consult the guide at [http://elasticsearch.org/guide](http://elasticsearch.org/guide).

# 

# The installation procedure is covered at

# [http://elasticsearch.org/guide/en/elasticsearch/reference/current/setup.html](http://elasticsearch.org/guide/en/elasticsearch/reference/current/setup.html).

# 

# ElasticSearch comes with reasonable defaults for most settings,

# so you can try it out without bothering with configuration.

# 

# Most of the time, these defaults are just fine for running a production

# cluster. If you're fine-tuning your cluster, or wondering about the

# effect of certain configuration option, please _do ask_ on the

# mailing list or IRC channel [[http://elasticsearch.org/community](http://elasticsearch.org/community)].

# Any element in the configuration can be replaced with environment variables

# by placing them in ${...} notation. For example:

# 

# node.rack: ${RACK\_ENV\_VAR}

# For information on supported formats and syntax for the config file, see

# [http://elasticsearch.org/guide/en/elasticsearch/reference/current/setup-configuration.html](http://elasticsearch.org/guide/en/elasticsearch/reference/current/setup-configuration.html)

################################### Cluster ###################################

# Cluster name identifies your cluster for auto-discovery. If you're running

# multiple clusters on the same network, make sure you're using unique names.

# 

cluster.name: elasticsearch

#################################### Node #####################################

# Node names are generated dynamically on startup, so you're relieved

# from configuring them manually. You can tie this node to a specific name:

# 

# node.name: "Franz Kafka"

# Every node can be configured to allow or deny being eligible as the master,

# and to allow or deny to store the data.

# 

# Allow this node to be eligible as a master node (enabled by default):

# 

# node.master: true

# 

# Allow this node to store data (enabled by default):

# 

# node.data: true

# You can exploit these settings to design advanced cluster topologies.

# 

# 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

# 

# 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.

# 

# node.master: true

# node.data: false

# 

# 3. You want this node to be neither master nor data node, but

# to act as a "search load balancer" (fetching data from nodes,

# aggregating results, etc.)

# 

# node.master: false

# node.data: false

# Use the Cluster Health API [[http://localhost:9200/\_cluster/health](http://localhost:9200/_cluster/health)], the

# Node Info API [[http://localhost:9200/\_cluster/nodes](http://localhost:9200/_cluster/nodes)] or GUI tools

# such as [http://github.com/lukas-vlcek/bigdesk](http://github.com/lukas-vlcek/bigdesk) and

# [http://mobz.github.com/elasticsearch-head](http://mobz.github.com/elasticsearch-head) to inspect the cluster state.

# A node can have generic attributes associated with it, which can later be used

# for customized shard allocation filtering, or allocation awareness. An attribute

# is a simple key value pair, similar to node.key: value, here is an example:

# 

# node.rack: rack314

# 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

#################################### Index ####################################

# You can set a number of options (such as shard/replica options, mapping

# or analyzer definitions, translog settings, ...) for indices globally,

# in this file.

# 

# Note, that it makes more sense to configure index settings specifically for

# a certain index, either when creating it or by using the index templates API.

# 

# See [http://elasticsearch.org/guide/en/elasticsearch/reference/current/index-modules.html](http://elasticsearch.org/guide/en/elasticsearch/reference/current/index-modules.html) and

# [http://elasticsearch.org/guide/en/elasticsearch/reference/current/indices-create-index.html](http://elasticsearch.org/guide/en/elasticsearch/reference/current/indices-create-index.html)

# for more information.

# Set the number of shards (splits) of an index (5 by default):

# 

# index.number\_of\_shards: 5

# Set the number of replicas (additional copies) of an index (1 by default):

# 

# index.number\_of\_replicas: 1

# Note, that for development on a local machine, with small indices, it usually

# makes sense to "disable" the distributed features:

# 

# index.number\_of\_shards: 1

# index.number\_of\_replicas: 0

# These settings directly affect the performance of index and search operations

# in your cluster. Assuming you have enough machines to hold shards and

# replicas, the rule of thumb is:

# 

# 1. Having more _shards_ enhances the _indexing_ performance and allows to

# _distribute_ a big index across machines.

# 2. Having more _replicas_ enhances the _search_ performance and improves the

# cluster _availability_.

# 

# The "number\_of\_shards" is a one-time setting for an index.

# 

# The "number\_of\_replicas" can be increased or decreased anytime,

# by using the Index Update Settings API.

# 

# ElasticSearch takes care about load balancing, relocating, gathering the

# results from nodes, etc. Experiment with different settings to fine-tune

# your setup.

# Use the Index Status API ([http://localhost:9200/A/\_status](http://localhost:9200/A/_status)) to inspect

# the index status.

#################################### Paths ####################################

# Path to directory containing configuration (this file and logging.yml):

# 

# path.conf: /path/to/conf

# Path to directory where to store index data allocated for this node.

# 

# path.data: /path/to/data

# 

# Can optionally include more than one location, causing data to be striped across

# the locations (a la RAID 0) on a file level, favouring locations with most free

# space on creation. For example:

# 

# path.data: /path/to/data1,/path/to/data2

# Path to temporary files:

# 

# path.work: /path/to/work

# Path to log files:

# 

# path.logs: /path/to/logs

# Path to where plugins are installed:

# 

# path.plugins: /path/to/plugins

#################################### Plugin ###################################

# If a plugin listed here is not installed for current node, the node will not start.

# 

# plugin.mandatory: mapper-attachments,lang-groovy

################################### Memory ####################################

# ElasticSearch performs poorly when JVM starts swapping: you should ensure that

# it _never_ swaps.

# 

# Set this property to true to lock the memory:

# 

# bootstrap.mlockall: true

# Make sure that the ES\_MIN\_MEM and ES\_MAX\_MEM environment variables are set

# to the same value, and that the machine has enough memory to allocate

# for ElasticSearch, leaving enough memory for the operating system itself.

# 

# You should also make sure that the ElasticSearch process is allowed to lock

# the memory, eg. by using `ulimit -l unlimited`.

############################## Network And HTTP ###############################

# ElasticSearch, by default, binds itself to the 0.0.0.0 address, and listens

# on port [9200-9300] for HTTP traffic and on port [9300-9400] for node-to-node

# communication. (the range means that if the port is busy, it will automatically

# try the next port).

# Set the bind address specifically (IPv4 or IPv6):

# 

# network.bind\_host: 192.168.0.1

# Set the address other nodes will use to communicate with this node. If not

# set, it is automatically derived. It must point to an actual IP address.

# 

# network.publish\_host: 192.168.0.1

# Set both 'bind\_host' and 'publish\_host':

# 

# network.host: 192.168.0.1

# Set a custom port for the node to node communication (9300 by default):

# 

# transport.tcp.port: 9300

# Enable compression for all communication between nodes (disabled by default):

# 

# transport.tcp.compress: true

# Set a custom port to listen for HTTP traffic:

# 

# http.port: 9200

# Set a custom allowed content length:

# 

# http.max\_content\_length: 100mb

# Disable HTTP completely:

# 

# http.enabled: false

################################### Gateway ###################################

# The gateway allows for persisting the cluster state between full cluster

# restarts. Every change to the state (such as adding an index) will be stored

# in the gateway, and when the cluster starts up for the first time,

# it will read its state from the gateway.

# There are several types of gateway implementations. For more information, see

# [http://elasticsearch.org/guide/en/elasticsearch/reference/current/modules-gateway.html](http://elasticsearch.org/guide/en/elasticsearch/reference/current/modules-gateway.html).

# The default gateway type is the "local" gateway (recommended):

# 

# gateway.type: local

# Settings below control how and when to start the initial recovery process on

# a full cluster restart (to reuse as much local data as possible when using shared

# gateway).

# Allow recovery process after N nodes in a cluster are up:

# 

# gateway.recover\_after\_nodes: 1

# Set the timeout to initiate the recovery process, once the N nodes

# from previous setting are up (accepts time value):

# 

# gateway.recover\_after\_time: 5m

# Set how many nodes are expected in this cluster. Once these N nodes

# are up (and recover\_after\_nodes is met), begin recovery process immediately

# (without waiting for recover\_after\_time to expire):

# 

# gateway.expected\_nodes: 2

############################# Recovery Throttling #############################

# These settings allow to control the process of shards allocation between

# nodes during initial recovery, replica allocation, rebalancing,

# or when adding and removing nodes.

# Set the number of concurrent recoveries happening on a node:

# 

# 1. During the initial recovery

# 

# cluster.routing.allocation.node\_initial\_primaries\_recoveries: 4

# 

# 2. During adding/removing nodes, rebalancing, etc

# 

# cluster.routing.allocation.node\_concurrent\_recoveries: 2

# Set to throttle throughput when recovering (eg. 100mb, by default 20mb):

# 

# indices.recovery.max\_bytes\_per\_sec: 20mb

# Set to limit the number of open concurrent streams when

# recovering a shard from a peer:

# 

# indices.recovery.concurrent\_streams: 5

################################## Discovery ##################################

# Discovery infrastructure ensures nodes can be found within a cluster

# 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. Its recommended to set it to a higher value

# than 1 when running more than 2 nodes in the cluster.

# 

# discovery.zen.minimum\_master\_nodes: 1

# 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

# to minimize discovery failures:

# 

# discovery.zen.ping.timeout: 3s

# For more information, see

# [http://elasticsearch.org/guide/en/elasticsearch/reference/current/modules-discovery-zen.html](http://elasticsearch.org/guide/en/elasticsearch/reference/current/modules-discovery-zen.html)

# Unicast discovery allows to explicitly control which nodes will be used

# to discover the cluster. It can be used when multicast is not present,

# or to restrict the cluster communication-wise.

# 

# 1. Disable multicast discovery (enabled by default):

# 

# 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: ["10.0.0.4", "10.0.0.5", "10.0.0.6"]

# EC2 discovery allows to use AWS EC2 API in order to perform discovery.

# 

# You have to install the cloud-aws plugin for enabling the EC2 discovery.

# 

# For more information, see

# [http://elasticsearch.org/guide/en/elasticsearch/reference/current/modules-discovery-ec2.html](http://elasticsearch.org/guide/en/elasticsearch/reference/current/modules-discovery-ec2.html)

# 

# See [http://elasticsearch.org/tutorials/elasticsearch-on-ec2/](http://elasticsearch.org/tutorials/elasticsearch-on-ec2/)

# for a step-by-step tutorial.

################################## Slow Log ##################################

# Shard level query and fetch threshold logging.

#index.search.slowlog.threshold.query.warn: 10s  
#index.search.slowlog.threshold.query.info: 5s  
#index.search.slowlog.threshold.query.debug: 2s  
#index.search.slowlog.threshold.query.trace: 500ms  
#index.search.slowlog.threshold.fetch.warn: 1s  
#index.search.slowlog.threshold.fetch.info: 800ms  
#index.search.slowlog.threshold.fetch.debug: 500ms  
#index.search.slowlog.threshold.fetch.trace: 200ms  
#index.indexing.slowlog.threshold.index.warn: 10s  
#index.indexing.slowlog.threshold.index.info: 5s  
#index.indexing.slowlog.threshold.index.debug: 2s  
#index.indexing.slowlog.threshold.index.trace: 500ms  
################################## GC Logging ################################  
#monitor.jvm.gc.young.warn: 1000ms  
#monitor.jvm.gc.young.info: 700ms  
#monitor.jvm.gc.young.debug: 400ms  
#monitor.jvm.gc.old.warn: 10s  
#monitor.jvm.gc.old.info: 5s  
#monitor.jvm.gc.old.debug: 2s  
################################# AZURE PLUGIN ###############################  
cloud:  
azure:  
keystore: c:/Certs/certificate.pfx  
password: password  
subscription\_id: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx  
service\_name: apw-es-vms  
discovery:  
type: azure

Cluster 2 - brand new clean cluster with same base configuration and only differences in elasticsearch.yml file are subscription id, service name and cluster name. Once again none of the nodes in this configuration can see each other.

I suspect this is a configuration issue but my experience with elasticsearch is limited. Does anyone have any ideas what I could have configured incorrectly?

Thanks

## Andrew

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 [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/12cca085-c7db-440e-8740-0bb973ff68a5%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/12cca085-c7db-440e-8740-0bb973ff68a5%40googlegroups.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

--  
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 [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/158117B5-996D-45D9-8BD5-8B9F1DB4D6B0%40pilato.fr](https://groups.google.com/d/msgid/elasticsearch/158117B5-996D-45D9-8BD5-8B9F1DB4D6B0%40pilato.fr).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![Andrew\_Westgarth](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/andrew_westgarth/32/1823_2.png) [@Andrew\_Westgarth](https://discuss.elastic.co/u/Andrew_Westgarth)\
**Post date:** [February 4, 2014, 10:47pm UTC](https://discuss.elastic.co/t/azure-cloud-plugin-problems/15600/3 "2014-02-04T22:47:35Z")

</div>

Hi David,  
here's the gist for the logs from the three nodes of Cluster 2

- [es node logs · GitHub](https://gist.github.com/apwestgarth/8813941) first thing I noticed which  
is strange is node 1 is referring to the cluster as sageerpdev\_escluster  
whereas node 2 and 3 are correctly referring to it as sageerpdevescluster.  
The config files (elasticsearch,yml) are the same on each node :s so not  
sure why that's happening.

I've since reverted cluster 1 back to unicast mode so I can carry on  
working with the old environment.

Thanks

Andrew

On Tuesday, 4 February 2014 22:22:49 UTC, David Pilato wrote:

> Could you please GIST your logs on both nodes?  
> Also, could you change Log level to TRACE for discovery? (See  
> config/logging.yml file)
> 
> Thanks
> 
> --  
> David 😉  
> Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs
> 
> Le 4 févr. 2014 à 22:42, Andrew Westgarth \<[ma...@hawaythelads.co.uk](mailto:ma...@hawaythelads.co.uk)\<javascript:\>\>  
> a écrit :
> 
> Hi,  
> I read with interest the news about the Azure Cloud Plugin over the  
> weekend and today have been trying to get it working with Windows VMs on  
> Azure with mixed levels of success.
> 
> I have two environments/clusters one which has been running for a few  
> weeks and another which is brand new and only been running for a couple of  
> days; both have the head plugin installed so I can see the status of the  
> cluster(s).
> 
> All of the clusters consist of 3 machines are using the Windows Server  
> 2012 R2 Datacenter base image with java 7 added, and elasticsearch 0.90.10  
> installed as a service set to automatic startup.
> 
> Cluster 1 - been running using multicast discovery disabled and the ip  
> addresses of the nodes listed. I have since installed the azure cloud  
> plugin, added the certificate and configuration to the node and enabled  
> multicast discovery again and commented out the list of ip addresses. Now  
> when I view the details of the cluster, none of the nodes can see each  
> other and the cluster health status is marked in amber as the full cluster  
> is no longer available.
> 
> the elasticsearch.yml file is as follows:
> 
> ##################### Elasticsearch Configuration Example  
> #####################
> 
> # This file contains an overview of various configuration settings,
> 
> # targeted at operations staff. Application developers should
> 
> # consult the guide at [http://elasticsearch.org/guide](http://elasticsearch.org/guide).
> 
> # 
> 
> # The installation procedure is covered at
> 
> # \<
> 
> [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://elasticsearch.org/guide/en/elasticsearch/reference/current/setup.html)
> 
> > .
> 
> # 
> 
> # Elasticsearch comes with reasonable defaults for most settings,
> 
> # so you can try it out without bothering with configuration.
> 
> # 
> 
> # Most of the time, these defaults are just fine for running a production
> 
> # cluster. If you're fine-tuning your cluster, or wondering about the
> 
> # effect of certain configuration option, please _do ask_ on the
> 
> # mailing list or IRC channel [[Elasticsearch Platform — Find real-time answers at scale | Elastic](http://elasticsearch.org/community)].
> 
> # Any element in the configuration can be replaced with environment
> 
> variables
> 
> # by placing them in ${...} notation. For example:
> 
> # 
> 
> # node.rack: ${RACK\_ENV\_VAR}
> 
> # For information on supported formats and syntax for the config file, see
> 
> # \<
> 
> [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://elasticsearch.org/guide/en/elasticsearch/reference/current/setup-configuration.html)
> 
> > 
> 
> ################################### Cluster  
> ###################################
> 
> # Cluster name identifies your cluster for auto-discovery. If you're
> 
> running
> 
> # multiple clusters on the same network, make sure you're using unique
> 
> names.
> 
> # 
> 
> cluster.name: elasticsearch
> 
> #################################### Node  
> #####################################
> 
> # Node names are generated dynamically on startup, so you're relieved
> 
> # from configuring them manually. You can tie this node to a specific name:
> 
> # 
> 
> # node.name: "Franz Kafka"
> 
> # Every node can be configured to allow or deny being eligible as the
> 
> master,
> 
> # and to allow or deny to store the data.
> 
> # 
> 
> # Allow this node to be eligible as a master node (enabled by default):
> 
> # 
> 
> # node.master: true
> 
> # 
> 
> # Allow this node to store data (enabled by default):
> 
> # 
> 
> # node.data: true
> 
> # You can exploit these settings to design advanced cluster topologies.
> 
> # 
> 
> # 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
> 
> # 
> 
> # 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.
> 
> # 
> 
> # node.master: true
> 
> # node.data: false
> 
> # 
> 
> # 3. You want this node to be neither master nor data node, but
> 
> # to act as a "search load balancer" (fetching data from nodes,
> 
> # aggregating results, etc.)
> 
> # 
> 
> # node.master: false
> 
> # node.data: false
> 
> # Use the Cluster Health API [[http://localhost:9200/\_cluster/health](http://localhost:9200/_cluster/health)], the
> 
> # Node Info API [[http://localhost:9200/\_cluster/nodes](http://localhost:9200/_cluster/nodes)] or GUI tools
> 
> # such as [http://github.com/lukas-vlcek/bigdesk](http://github.com/lukas-vlcek/bigdesk) and
> 
> # [http://mobz.github.com/elasticsearch-head](http://mobz.github.com/elasticsearch-head) to inspect the cluster
> 
> state.
> 
> # A node can have generic attributes associated with it, which can later
> 
> be used
> 
> # for customized shard allocation filtering, or allocation awareness. An
> 
> attribute
> 
> # is a simple key value pair, similar to node.key: value, here is an
> 
> example:
> 
> # 
> 
> # node.rack: rack314
> 
> # 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
> 
> #################################### Index  
> ####################################
> 
> # You can set a number of options (such as shard/replica options, mapping
> 
> # or analyzer definitions, translog settings, ...) for indices globally,
> 
> # in this file.
> 
> # 
> 
> # Note, that it makes more sense to configure index settings specifically
> 
> for
> 
> # a certain index, either when creating it or by using the index templates
> 
> API.
> 
> # 
> 
> # See \<
> 
> [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://elasticsearch.org/guide/en/elasticsearch/reference/current/index-modules.html)\>  
> and
> 
> # \<
> 
> [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://elasticsearch.org/guide/en/elasticsearch/reference/current/indices-create-index.html)
> 
> > 
> 
> # for more information.
> 
> # Set the number of shards (splits) of an index (5 by default):
> 
> # 
> 
> # index.number\_of\_shards: 5
> 
> # Set the number of replicas (additional copies) of an index (1 by
> 
> default):
> 
> # 
> 
> # index.number\_of\_replicas: 1
> 
> # Note, that for development on a local machine, with small indices, it
> 
> usually
> 
> # makes sense to "disable" the distributed features:
> 
> # 
> 
> # index.number\_of\_shards: 1
> 
> # index.number\_of\_replicas: 0
> 
> # These settings directly affect the performance of index and search
> 
> operations
> 
> # in your cluster. Assuming you have enough machines to hold shards and
> 
> # replicas, the rule of thumb is:
> 
> # 
> 
> # 1. Having more _shards_ enhances the _indexing_ performance and allows to
> 
> # _distribute_ a big index across machines.
> 
> # 2. Having more _replicas_ enhances the _search_ performance and improves
> 
> the
> 
> # cluster _availability_.
> 
> # 
> 
> # The "number\_of\_shards" is a one-time setting for an index.
> 
> # 
> 
> # The "number\_of\_replicas" can be increased or decreased anytime,
> 
> # by using the Index Update Settings API.
> 
> # 
> 
> # Elasticsearch takes care about load balancing, relocating, gathering the
> 
> # results from nodes, etc. Experiment with different settings to fine-tune
> 
> # your setup.
> 
> # Use the Index Status API ([http://localhost:9200/A/\_status](http://localhost:9200/A/_status)) to inspect
> 
> # the index status.
> 
> #################################### Paths  
> ####################################
> 
> # Path to directory containing configuration (this file and logging.yml):
> 
> # 
> 
> # path.conf: /path/to/conf
> 
> # Path to directory where to store index data allocated for this node.
> 
> # 
> 
> # path.data: /path/to/data
> 
> # 
> 
> # Can optionally include more than one location, causing data to be
> 
> striped across
> 
> # the locations (a la RAID 0) on a file level, favouring locations with
> 
> most free
> 
> # space on creation. For example:
> 
> # 
> 
> # path.data: /path/to/data1,/path/to/data2
> 
> # Path to temporary files:
> 
> # 
> 
> # path.work: /path/to/work
> 
> # Path to log files:
> 
> # 
> 
> # path.logs: /path/to/logs
> 
> # Path to where plugins are installed:
> 
> # 
> 
> # path.plugins: /path/to/plugins
> 
> #################################### Plugin  
> ###################################
> 
> # If a plugin listed here is not installed for current node, the node will
> 
> not start.
> 
> # 
> 
> # plugin.mandatory: mapper-attachments,lang-groovy
> 
> ################################### Memory  
> ####################################
> 
> # Elasticsearch performs poorly when JVM starts swapping: you should
> 
> ensure that
> 
> # it _never_ swaps.
> 
> # 
> 
> # Set this property to true to lock the memory:
> 
> # 
> 
> # bootstrap.mlockall: true
> 
> # Make sure that the ES\_MIN\_MEM and ES\_MAX\_MEM environment variables are
> 
> set
> 
> # to the same value, and that the machine has enough memory to allocate
> 
> # for Elasticsearch, leaving enough memory for the operating system itself.
> 
> # 
> 
> # You should also make sure that the Elasticsearch process is allowed to
> 
> lock
> 
> # the memory, eg. by using `ulimit -l unlimited`.
> 
> ############################## Network And HTTP  
> ###############################
> 
> # Elasticsearch, by default, binds itself to the 0.0.0.0 address, and
> 
> listens
> 
> # on port [9200-9300] for HTTP traffic and on port [9300-9400] for
> 
> node-to-node
> 
> # communication. (the range means that if the port is busy, it will
> 
> automatically
> 
> # try the next port).
> 
> # Set the bind address specifically (IPv4 or IPv6):
> 
> # 
> 
> # network.bind\_host: 192.168.0.1
> 
> # Set the address other nodes will use to communicate with this node. If
> 
> not
> 
> # set, it is automatically derived. It must point to an actual IP address.
> 
> # 
> 
> # network.publish\_host: 192.168.0.1
> 
> # Set both 'bind\_host' and 'publish\_host':
> 
> # 
> 
> # network.host: 192.168.0.1
> 
> # Set a custom port for the node to node communication (9300 by default):
> 
> # 
> 
> # transport.tcp.port: 9300
> 
> # Enable compression for all communication between nodes (disabled by
> 
> default):
> 
> # 
> 
> # transport.tcp.compress: true
> 
> # Set a custom port to listen for HTTP traffic:
> 
> # 
> 
> # http.port: 9200
> 
> # Set a custom allowed content length:
> 
> # 
> 
> # http.max\_content\_length: 100mb
> 
> # Disable HTTP completely:
> 
> # 
> 
> # http.enabled: false
> 
> ################################### Gateway  
> ###################################
> 
> # The gateway allows for persisting the cluster state between full cluster
> 
> # restarts. Every change to the state (such as adding an index) will be
> 
> stored
> 
> # in the gateway, and when the cluster starts up for the first time,
> 
> # it will read its state from the gateway.
> 
> # There are several types of gateway implementations. For more
> 
> information, see
> 
> # \<
> 
> [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://elasticsearch.org/guide/en/elasticsearch/reference/current/modules-gateway.html)
> 
> > .
> 
> # The default gateway type is the "local" gateway (recommended):
> 
> # 
> 
> # gateway.type: local
> 
> # Settings below control how and when to start the initial recovery
> 
> process on
> 
> # a full cluster restart (to reuse as much local data as possible when
> 
> using shared
> 
> # gateway).
> 
> # Allow recovery process after N nodes in a cluster are up:
> 
> # 
> 
> # gateway.recover\_after\_nodes: 1
> 
> # Set the timeout to initiate the recovery process, once the N nodes
> 
> # from previous setting are up (accepts time value):
> 
> # 
> 
> # gateway.recover\_after\_time: 5m
> 
> # Set how many nodes are expected in this cluster. Once these N nodes
> 
> # are up (and recover\_after\_nodes is met), begin recovery process
> 
> immediately
> 
> # (without waiting for recover\_after\_time to expire):
> 
> # 
> 
> # gateway.expected\_nodes: 2
> 
> ############################# Recovery Throttling  
> #############################
> 
> # These settings allow to control the process of shards allocation between
> 
> # nodes during initial recovery, replica allocation, rebalancing,
> 
> # or when adding and removing nodes.
> 
> # Set the number of concurrent recoveries happening on a node:
> 
> # 
> 
> # 1. During the initial recovery
> 
> # 
> 
> # cluster.routing.allocation.node\_initial\_primaries\_recoveries: 4
> 
> # 
> 
> # 2. During adding/removing nodes, rebalancing, etc
> 
> # 
> 
> # cluster.routing.allocation.node\_concurrent\_recoveries: 2
> 
> # Set to throttle throughput when recovering (eg. 100mb, by default 20mb):
> 
> # 
> 
> # indices.recovery.max\_bytes\_per\_sec: 20mb
> 
> # Set to limit the number of open concurrent streams when
> 
> # recovering a shard from a peer:
> 
> # 
> 
> # indices.recovery.concurrent\_streams: 5
> 
> ################################## Discovery  
> ##################################
> 
> # Discovery infrastructure ensures nodes can be found within a cluster
> 
> # 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. Its recommended to set it to a higher
> 
> value
> 
> # than 1 when running more than 2 nodes in the cluster.
> 
> # 
> 
> # discovery.zen.minimum\_master\_nodes: 1
> 
> # 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
> 
> # to minimize discovery failures:
> 
> # 
> 
> # discovery.zen.ping.timeout: 3s
> 
> # For more information, see
> 
> # \<
> 
> [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://elasticsearch.org/guide/en/elasticsearch/reference/current/modules-discovery-zen.html)
> 
> > 
> 
> # Unicast discovery allows to explicitly control which nodes will be used
> 
> # to discover the cluster. It can be used when multicast is not present,
> 
> # or to restrict the cluster communication-wise.
> 
> # 
> 
> # 1. Disable multicast discovery (enabled by default):
> 
> # 
> 
> # 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: ["10.0.0.4", "10.0.0.5", "10.0.0.6"]
> 
> # EC2 discovery allows to use AWS EC2 API in order to perform discovery.
> 
> # 
> 
> # You have to install the cloud-aws plugin for enabling the EC2 discovery.
> 
> # 
> 
> # For more information, see
> 
> # \<
> 
> [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://elasticsearch.org/guide/en/elasticsearch/reference/current/modules-discovery-ec2.html)
> 
> > 
> 
> # 
> 
> # See [http://elasticsearch.org/tutorials/elasticsearch-on-ec2/](http://elasticsearch.org/tutorials/elasticsearch-on-ec2/)
> 
> # for a step-by-step tutorial.
> 
> ################################## Slow Log  
> ##################################
> 
> # Shard level query and fetch threshold logging.
> 
> #index.search.slowlog.threshold.query.warn: 10s  
> #index.search.slowlog.threshold.query.info: 5s  
> #index.search.slowlog.threshold.query.debug: 2s  
> #index.search.slowlog.threshold.query.trace: 500ms  
> #index.search.slowlog.threshold.fetch.warn: 1s  
> #index.search.slowlog.threshold.fetch.info: 800ms  
> #index.search.slowlog.threshold.fetch.debug: 500ms  
> #index.search.slowlog.threshold.fetch.trace: 200ms  
> #index.indexing.slowlog.threshold.index.warn: 10s  
> #index.indexing.slowlog.threshold.index.info: 5s  
> #index.indexing.slowlog.threshold.index.debug: 2s  
> #index.indexing.slowlog.threshold.index.trace: 500ms  
> ################################## GC Logging  
> ################################  
> #monitor.jvm.gc.young.warn: 1000ms  
> #monitor.jvm.gc.young.info: 700ms  
> #monitor.jvm.gc.young.debug: 400ms  
> #monitor.jvm.gc.old.warn: 10s  
> #monitor.jvm.gc.old.info: 5s  
> #monitor.jvm.gc.old.debug: 2s  
> ################################# AZURE PLUGIN  
> ###############################  
> cloud:  
> azure:  
> keystore: c:/Certs/certificate.pfx  
> password: password  
> subscription\_id: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx  
> service\_name: apw-es-vms  
> discovery:  
> type: azure
> 
> Cluster 2 - brand new clean cluster with same base configuration and only  
> differences in elasticsearch.yml file are subscription id, service name and  
> cluster name. Once again none of the nodes in this configuration can see  
> each other.
> 
> I suspect this is a configuration issue but my experience with  
> elasticsearch is limited. Does anyone have any ideas what I could have  
> configured incorrectly?
> 
> Thanks
> 
> Andrew
> 
> --  
> 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 [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com) \<javascript:\>.  
> To view this discussion on the web visit  
> [https://groups.google.com/d/msgid/elasticsearch/12cca085-c7db-440e-8740-0bb973ff68a5%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/12cca085-c7db-440e-8740-0bb973ff68a5%40googlegroups.com)  
> .  
> For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

--  
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 [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/f322a3b4-733f-4718-a051-0654e4d38ab2%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/f322a3b4-733f-4718-a051-0654e4d38ab2%40googlegroups.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [February 5, 2014, 8:17am UTC](https://discuss.elastic.co/t/azure-cloud-plugin-problems/15600/4 "2014-02-05T08:17:52Z")

</div>

So Azure plugin actually does not start but only multicast discovery.

I think it's because your elasticsearch.yml is not correct. Probably because a line is missing between cloud and discovery parts.  
Also indentation can play a role here I guess (discovery should be indented at the same level as cloud and not inside cloud).

cloud:  
azure:  
keystore: c:/Certs/certificate.pfx  
password: password  
subscription\_id: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx  
service\_name: apw-es-vms  
discovery:  
type: azure

I created a GIST here of something which should work: [https://gist.github.com/dadoonet/8819191](https://gist.github.com/dadoonet/8819191)

Hope this helps

--  
David Pilato | Technical Advocate | [Elasticsearch.com](http://Elasticsearch.com)  
@dadoonet | @elasticsearchfr

Le 4 février 2014 at 23:47:39, Andrew Westgarth (mail@hawaythelads.co.uk) a écrit:

Hi David,  
here's the gist for the logs from the three nodes of Cluster 2 - [https://gist.github.com/apwestgarth/8813941](https://gist.github.com/apwestgarth/8813941) first thing I noticed which is strange is node 1 is referring to the cluster as sageerpdev\_escluster whereas node 2 and 3 are correctly referring to it as sageerpdevescluster. The config files (elasticsearch,yml) are the same on each node :s so not sure why that's happening.

I've since reverted cluster 1 back to unicast mode so I can carry on working with the old environment.

Thanks

Andrew

On Tuesday, 4 February 2014 22:22:49 UTC, David Pilato wrote:  
Could you please GIST your logs on both nodes?  
Also, could you change Log level to TRACE for discovery? (See config/logging.yml file)

Thanks

--  
David 😉  
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs

Le 4 févr. 2014 à 22:42, Andrew Westgarth [ma...@hawaythelads.co.uk](mailto:ma...@hawaythelads.co.uk) a écrit :

Hi,  
I read with interest the news about the Azure Cloud Plugin over the weekend and today have been trying to get it working with Windows VMs on Azure with mixed levels of success.

I have two environments/clusters one which has been running for a few weeks and another which is brand new and only been running for a couple of days; both have the head plugin installed so I can see the status of the cluster(s).

All of the clusters consist of 3 machines are using the Windows Server 2012 R2 Datacenter base image with java 7 added, and elasticsearch 0.90.10 installed as a service set to automatic startup.

Cluster 1 - been running using multicast discovery disabled and the ip addresses of the nodes listed. I have since installed the azure cloud plugin, added the certificate and configuration to the node and enabled multicast discovery again and commented out the list of ip addresses. Now when I view the details of the cluster, none of the nodes can see each other and the cluster health status is marked in amber as the full cluster is no longer available.

the elasticsearch.yml file is as follows:

##################### ElasticSearch Configuration Example #####################

# This file contains an overview of various configuration settings,

# targeted at operations staff. Application developers should

# consult the guide at [http://elasticsearch.org/guide](http://elasticsearch.org/guide).

# 

# The installation procedure is covered at

# [http://elasticsearch.org/guide/en/elasticsearch/reference/current/setup.html](http://elasticsearch.org/guide/en/elasticsearch/reference/current/setup.html).

# 

# ElasticSearch comes with reasonable defaults for most settings,

# so you can try it out without bothering with configuration.

# 

# Most of the time, these defaults are just fine for running a production

# cluster. If you're fine-tuning your cluster, or wondering about the

# effect of certain configuration option, please _do ask_ on the

# mailing list or IRC channel [[http://elasticsearch.org/community](http://elasticsearch.org/community)].

# Any element in the configuration can be replaced with environment variables

# by placing them in ${...} notation. For example:

# 

# node.rack: ${RACK\_ENV\_VAR}

# For information on supported formats and syntax for the config file, see

# [http://elasticsearch.org/guide/en/elasticsearch/reference/current/setup-configuration.html](http://elasticsearch.org/guide/en/elasticsearch/reference/current/setup-configuration.html)

################################### Cluster ###################################

# Cluster name identifies your cluster for auto-discovery. If you're running

# multiple clusters on the same network, make sure you're using unique names.

# 

cluster.name: elasticsearch

#################################### Node #####################################

# Node names are generated dynamically on startup, so you're relieved

# from configuring them manually. You can tie this node to a specific name:

# 

# node.name: "Franz Kafka"

# Every node can be configured to allow or deny being eligible as the master,

# and to allow or deny to store the data.

# 

# Allow this node to be eligible as a master node (enabled by default):

# 

# node.master: true

# 

# Allow this node to store data (enabled by default):

# 

# node.data: true

# You can exploit these settings to design advanced cluster topologies.

# 

# 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

# 

# 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.

# 

# node.master: true

# node.data: false

# 

# 3. You want this node to be neither master nor data node, but

# to act as a "search load balancer" (fetching data from nodes,

# aggregating results, etc.)

# 

# node.master: false

# node.data: false

# Use the Cluster Health API [[http://localhost:9200/\_cluster/health](http://localhost:9200/_cluster/health)], the

# Node Info API [[http://localhost:9200/\_cluster/nodes](http://localhost:9200/_cluster/nodes)] or GUI tools

# such as [http://github.com/lukas-vlcek/bigdesk](http://github.com/lukas-vlcek/bigdesk) and

# [http://mobz.github.com/elasticsearch-head](http://mobz.github.com/elasticsearch-head) to inspect the cluster state.

# A node can have generic attributes associated with it, which can later be used

# for customized shard allocation filtering, or allocation awareness. An attribute

# is a simple key value pair, similar to node.key: value, here is an example:

# 

# node.rack: rack314

# 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

#################################### Index ####################################

# You can set a number of options (such as shard/replica options, mapping

# or analyzer definitions, translog settings, ...) for indices globally,

# in this file.

# 

# Note, that it makes more sense to configure index settings specifically for

# a certain index, either when creating it or by using the index templates API.

# 

# See [http://elasticsearch.org/guide/en/elasticsearch/reference/current/index-modules.html](http://elasticsearch.org/guide/en/elasticsearch/reference/current/index-modules.html) and

# [http://elasticsearch.org/guide/en/elasticsearch/reference/current/indices-create-index.html](http://elasticsearch.org/guide/en/elasticsearch/reference/current/indices-create-index.html)

# for more information.

# Set the number of shards (splits) of an index (5 by default):

# 

# index.number\_of\_shards: 5

# Set the number of replicas (additional copies) of an index (1 by default):

# 

# index.number\_of\_replicas: 1

# Note, that for development on a local machine, with small indices, it usually

# makes sense to "disable" the distributed features:

# 

# index.number\_of\_shards: 1

# index.number\_of\_replicas: 0

# These settings directly affect the performance of index and search operations

# in your cluster. Assuming you have enough machines to hold shards and

# replicas, the rule of thumb is:

# 

# 1. Having more _shards_ enhances the _indexing_ performance and allows to

# _distribute_ a big index across machines.

# 2. Having more _replicas_ enhances the _search_ performance and improves the

# cluster _availability_.

# 

# The "number\_of\_shards" is a one-time setting for an index.

# 

# The "number\_of\_replicas" can be increased or decreased anytime,

# by using the Index Update Settings API.

# 

# ElasticSearch takes care about load balancing, relocating, gathering the

# results from nodes, etc. Experiment with different settings to fine-tune

# your setup.

# Use the Index Status API ([http://localhost:9200/A/\_status](http://localhost:9200/A/_status)) to inspect

# the index status.

#################################### Paths ####################################

# Path to directory containing configuration (this file and logging.yml):

# 

# path.conf: /path/to/conf

# Path to directory where to store index data allocated for this node.

# 

# path.data: /path/to/data

# 

# Can optionally include more than one location, causing data to be striped across

# the locations (a la RAID 0) on a file level, favouring locations with most free

# space on creation. For example:

# 

# path.data: /path/to/data1,/path/to/data2

# Path to temporary files:

# 

# path.work: /path/to/work

# Path to log files:

# 

# path.logs: /path/to/logs

# Path to where plugins are installed:

# 

# path.plugins: /path/to/plugins

#################################### Plugin ###################################

# If a plugin listed here is not installed for current node, the node will not start.

# 

# plugin.mandatory: mapper-attachments,lang-groovy

################################### Memory ####################################

# ElasticSearch performs poorly when JVM starts swapping: you should ensure that

# it _never_ swaps.

# 

# Set this property to true to lock the memory:

# 

# bootstrap.mlockall: true

# Make sure that the ES\_MIN\_MEM and ES\_MAX\_MEM environment variables are set

# to the same value, and that the machine has enough memory to allocate

# for ElasticSearch, leaving enough memory for the operating system itself.

# 

# You should also make sure that the ElasticSearch process is allowed to lock

# the memory, eg. by using `ulimit -l unlimited`.

############################## Network And HTTP ###############################

# ElasticSearch, by default, binds itself to the 0.0.0.0 address, and listens

# on port [9200-9300] for HTTP traffic and on port [9300-9400] for node-to-node

# communication. (the range means that if the port is busy, it will automatically

# try the next port).

# Set the bind address specifically (IPv4 or IPv6):

# 

# network.bind\_host: 192.168.0.1

# Set the address other nodes will use to communicate with this node. If not

# set, it is automatically derived. It must point to an actual IP address.

# 

# network.publish\_host: 192.168.0.1

# Set both 'bind\_host' and 'publish\_host':

# 

# network.host: 192.168.0.1

# Set a custom port for the node to node communication (9300 by default):

# 

# transport.tcp.port: 9300

# Enable compression for all communication between nodes (disabled by default):

# 

# transport.tcp.compress: true

# Set a custom port to listen for HTTP traffic:

# 

# http.port: 9200

# Set a custom allowed content length:

# 

# http.max\_content\_length: 100mb

# Disable HTTP completely:

# 

# http.enabled: false

################################### Gateway ###################################

# The gateway allows for persisting the cluster state between full cluster

# restarts. Every change to the state (such as adding an index) will be stored

# in the gateway, and when the cluster starts up for the first time,

# it will read its state from the gateway.

# There are several types of gateway implementations. For more information, see

# [http://elasticsearch.org/guide/en/elasticsearch/reference/current/modules-gateway.html](http://elasticsearch.org/guide/en/elasticsearch/reference/current/modules-gateway.html).

# The default gateway type is the "local" gateway (recommended):

# 

# gateway.type: local

# Settings below control how and when to start the initial recovery process on

# a full cluster restart (to reuse as much local data as possible when using shared

# gateway).

# Allow recovery process after N nodes in a cluster are up:

# 

# gateway.recover\_after\_nodes: 1

# Set the timeout to initiate the recovery process, once the N nodes

# from previous setting are up (accepts time value):

# 

# gateway.recover\_after\_time: 5m

# Set how many nodes are expected in this cluster. Once these N nodes

# are up (and recover\_after\_nodes is met), begin recovery process immediately

# (without waiting for recover\_after\_time to expire):

# 

# gateway.expected\_nodes: 2

############################# Recovery Throttling #############################

# These settings allow to control the process of shards allocation between

# nodes during initial recovery, replica allocation, rebalancing,

# or when adding and removing nodes.

# Set the number of concurrent recoveries happening on a node:

# 

# 1. During the initial recovery

# 

# cluster.routing.allocation.node\_initial\_primaries\_recoveries: 4

# 

# 2. During adding/removing nodes, rebalancing, etc

# 

# cluster.routing.allocation.node\_concurrent\_recoveries: 2

# Set to throttle throughput when recovering (eg. 100mb, by default 20mb):

# 

# indices.recovery.max\_bytes\_per\_sec: 20mb

# Set to limit the number of open concurrent streams when

# recovering a shard from a peer:

# 

# indices.recovery.concurrent\_streams: 5

################################## Discovery ##################################

# Discovery infrastructure ensures nodes can be found within a cluster

# 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. Its recommended to set it to a higher value

# than 1 when running more than 2 nodes in the cluster.

# 

# discovery.zen.minimum\_master\_nodes: 1

# 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

# to minimize discovery failures:

# 

# discovery.zen.ping.timeout: 3s

# For more information, see

# [http://elasticsearch.org/guide/en/elasticsearch/reference/current/modules-discovery-zen.html](http://elasticsearch.org/guide/en/elasticsearch/reference/current/modules-discovery-zen.html)

# Unicast discovery allows to explicitly control which nodes will be used

# to discover the cluster. It can be used when multicast is not present,

# or to restrict the cluster communication-wise.

# 

# 1. Disable multicast discovery (enabled by default):

# 

# 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: ["10.0.0.4", "10.0.0.5", "10.0.0.6"]

# EC2 discovery allows to use AWS EC2 API in order to perform discovery.

# 

# You have to install the cloud-aws plugin for enabling the EC2 discovery.

# 

# For more information, see

# [http://elasticsearch.org/guide/en/elasticsearch/reference/current/modules-discovery-ec2.html](http://elasticsearch.org/guide/en/elasticsearch/reference/current/modules-discovery-ec2.html)

# 

# See [http://elasticsearch.org/tutorials/elasticsearch-on-ec2/](http://elasticsearch.org/tutorials/elasticsearch-on-ec2/)

# for a step-by-step tutorial.

################################## Slow Log ##################################

# Shard level query and fetch threshold logging.

#index.search.slowlog.threshold.query.warn: 10s  
#index.search.slowlog.threshold.query.info: 5s  
#index.search.slowlog.threshold.query.debug: 2s  
#index.search.slowlog.threshold.query.trace: 500ms  
#index.search.slowlog.threshold.fetch.warn: 1s  
#index.search.slowlog.threshold.fetch.info: 800ms  
#index.search.slowlog.threshold.fetch.debug: 500ms  
#index.search.slowlog.threshold.fetch.trace: 200ms  
#index.indexing.slowlog.threshold.index.warn: 10s  
#index.indexing.slowlog.threshold.index.info: 5s  
#index.indexing.slowlog.threshold.index.debug: 2s  
#index.indexing.slowlog.threshold.index.trace: 500ms  
################################## GC Logging ################################  
#monitor.jvm.gc.young.warn: 1000ms  
#monitor.jvm.gc.young.info: 700ms  
#monitor.jvm.gc.young.debug: 400ms  
#monitor.jvm.gc.old.warn: 10s  
#monitor.jvm.gc.old.info: 5s  
#monitor.jvm.gc.old.debug: 2s  
################################# AZURE PLUGIN ###############################  
cloud:  
azure:  
keystore: c:/Certs/certificate.pfx  
password: password  
subscription\_id: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx  
service\_name: apw-es-vms  
discovery:  
type: azure

Cluster 2 - brand new clean cluster with same base configuration and only differences in elasticsearch.yml file are subscription id, service name and cluster name. Once again none of the nodes in this configuration can see each other.

I suspect this is a configuration issue but my experience with elasticsearch is limited. Does anyone have any ideas what I could have configured incorrectly?

Thanks

## Andrew

## 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 [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/12cca085-c7db-440e-8740-0bb973ff68a5%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/12cca085-c7db-440e-8740-0bb973ff68a5%40googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

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 [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/f322a3b4-733f-4718-a051-0654e4d38ab2%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/f322a3b4-733f-4718-a051-0654e4d38ab2%40googlegroups.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

--  
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 [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/etPan.52f1f3b0.3f2dba31.d955%40MacBook-Air-de-David.local](https://groups.google.com/d/msgid/elasticsearch/etPan.52f1f3b0.3f2dba31.d955%40MacBook-Air-de-David.local).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![Andrew\_Westgarth](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/andrew_westgarth/32/1823_2.png) [@Andrew\_Westgarth](https://discuss.elastic.co/u/Andrew_Westgarth)\
**Post date:** [February 5, 2014, 9:34am UTC](https://discuss.elastic.co/t/azure-cloud-plugin-problems/15600/5 "2014-02-05T09:34:42Z")

</div>

Hi David,  
thanks for taking a look and creating the new GIST. I've  
uploaded an updated elasticsearch.yml file and all are now being seen by  
each other! 🙂 I also resolved the issue on node 1 as it had two config  
files, one in the root which was overriding one in the config directory.

One thing I'm learning about Elasticsearch over the last month is that the  
yml files are very particular about format and it's very easy to get it  
wrong despite using tooling (I was using a visual studio plugin and am now  
using Notepad++ and still didn't see the issues)

Thanks for your help, I'll update my draft blog post and publish this  
morning.

Thanks

Andrew

On Wednesday, 5 February 2014 08:17:52 UTC, David Pilato wrote:

> So Azure plugin actually does not start but only multicast discovery.
> 
> I think it's because your elasticsearch.yml is not correct. Probably  
> because a line is missing between cloud and discovery parts.  
> Also indentation can play a role here I guess (discovery should be  
> indented at the same level as cloud and not inside cloud).
> 
> cloud:  
> azure:  
> keystore: c:/Certs/certificate.pfx  
> password: password  
> subscription\_id: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx  
> service\_name: apw-es-vms  
> discovery:  
> type: azure
> 
> I created a GIST here of something which should work:  
> [elasticsearch yaml example for azure plugin · GitHub](https://gist.github.com/dadoonet/8819191)
> 
> Hope this helps
> 
> --  
> _David Pilato_ | _Technical Advocate_ | _[Elasticsearch.com](http://Elasticsearch.com)_  
> @dadoonet [https://twitter.com/dadoonet](https://twitter.com/dadoonet) | @elasticsearchfr[https://twitter.com/elasticsearchfr](https://twitter.com/elasticsearchfr)
> 
> Le 4 février 2014 at 23:47:39, Andrew Westgarth ([ma...@hawaythelads.co.uk](mailto:ma...@hawaythelads.co.uk)\<javascript:\>)  
> a écrit:
> 
> Hi David,  
> here's the gist for the logs from the three nodes of Cluster 2
> 
> - [es node logs · GitHub](https://gist.github.com/apwestgarth/8813941) first thing I noticed which  
> is strange is node 1 is referring to the cluster as sageerpdev\_escluster  
> whereas node 2 and 3 are correctly referring to it as sageerpdevescluster.  
> The config files (elasticsearch,yml) are the same on each node :s so not  
> sure why that's happening.
> 
> I've since reverted cluster 1 back to unicast mode so I can carry on  
> working with the old environment.
> 
> Thanks
> 
> Andrew
> 
> On Tuesday, 4 February 2014 22:22:49 UTC, David Pilato wrote:
> 
> > Could you please GIST your logs on both nodes?  
> > Also, could you change Log level to TRACE for discovery? (See  
> > config/logging.yml file)
> > 
> > Thanks
> > 
> > --  
> > David 😉  
> > Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs
> > 
> > Le 4 févr. 2014 à 22:42, Andrew Westgarth [ma...@hawaythelads.co.uk](mailto:ma...@hawaythelads.co.uk) a  
> > écrit :
> > 
> > Hi,  
> > I read with interest the news about the Azure Cloud Plugin over the  
> > weekend and today have been trying to get it working with Windows VMs on  
> > Azure with mixed levels of success.
> > 
> > I have two environments/clusters one which has been running for a few  
> > weeks and another which is brand new and only been running for a couple of  
> > days; both have the head plugin installed so I can see the status of the  
> > cluster(s).
> > 
> > All of the clusters consist of 3 machines are using the Windows Server  
> > 2012 R2 Datacenter base image with java 7 added, and elasticsearch 0.90.10  
> > installed as a service set to automatic startup.
> > 
> > Cluster 1 - been running using multicast discovery disabled and the ip  
> > addresses of the nodes listed. I have since installed the azure cloud  
> > plugin, added the certificate and configuration to the node and enabled  
> > multicast discovery again and commented out the list of ip addresses. Now  
> > when I view the details of the cluster, none of the nodes can see each  
> > other and the cluster health status is marked in amber as the full cluster  
> > is no longer available.
> > 
> > the elasticsearch.yml file is as follows:
> > 
> > ##################### Elasticsearch Configuration Example  
> > #####################
> > 
> > # This file contains an overview of various configuration settings,
> > 
> > # targeted at operations staff. Application developers should
> > 
> > # consult the guide at [http://elasticsearch.org/guide](http://elasticsearch.org/guide).
> > 
> > # 
> > 
> > # The installation procedure is covered at
> > 
> > # \<
> > 
> > [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://elasticsearch.org/guide/en/elasticsearch/reference/current/setup.html)
> > 
> > > .
> > 
> > # 
> > 
> > # Elasticsearch comes with reasonable defaults for most settings,
> > 
> > # so you can try it out without bothering with configuration.
> > 
> > # 
> > 
> > # Most of the time, these defaults are just fine for running a production
> > 
> > # cluster. If you're fine-tuning your cluster, or wondering about the
> > 
> > # effect of certain configuration option, please _do ask_ on the
> > 
> > # mailing list or IRC channel [[Elasticsearch Platform — Find real-time answers at scale | Elastic](http://elasticsearch.org/community)].
> > 
> > # Any element in the configuration can be replaced with environment
> > 
> > variables
> > 
> > # by placing them in ${...} notation. For example:
> > 
> > # 
> > 
> > # node.rack: ${RACK\_ENV\_VAR}
> > 
> > # For information on supported formats and syntax for the config file, see
> > 
> > # \<
> > 
> > [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://elasticsearch.org/guide/en/elasticsearch/reference/current/setup-configuration.html)
> > 
> > > 
> > 
> > ################################### Cluster  
> > ###################################
> > 
> > # Cluster name identifies your cluster for auto-discovery. If you're
> > 
> > running
> > 
> > # multiple clusters on the same network, make sure you're using unique
> > 
> > names.
> > 
> > # 
> > 
> > cluster.name: elasticsearch
> > 
> > #################################### Node  
> > #####################################
> > 
> > # Node names are generated dynamically on startup, so you're relieved
> > 
> > # from configuring them manually. You can tie this node to a specific
> > 
> > name:
> > 
> > # 
> > 
> > # node.name: "Franz Kafka"
> > 
> > # Every node can be configured to allow or deny being eligible as the
> > 
> > master,
> > 
> > # and to allow or deny to store the data.
> > 
> > # 
> > 
> > # Allow this node to be eligible as a master node (enabled by default):
> > 
> > # 
> > 
> > # node.master: true
> > 
> > # 
> > 
> > # Allow this node to store data (enabled by default):
> > 
> > # 
> > 
> > # node.data: true
> > 
> > # You can exploit these settings to design advanced cluster topologies.
> > 
> > # 
> > 
> > # 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
> > 
> > # 
> > 
> > # 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.
> > 
> > # 
> > 
> > # node.master: true
> > 
> > # node.data: false
> > 
> > # 
> > 
> > # 3. You want this node to be neither master nor data node, but
> > 
> > # to act as a "search load balancer" (fetching data from nodes,
> > 
> > # aggregating results, etc.)
> > 
> > # 
> > 
> > # node.master: false
> > 
> > # node.data: false
> > 
> > # Use the Cluster Health API [[http://localhost:9200/\_cluster/health](http://localhost:9200/_cluster/health)], the
> > 
> > # Node Info API [[http://localhost:9200/\_cluster/nodes](http://localhost:9200/_cluster/nodes)] or GUI tools
> > 
> > # such as [http://github.com/lukas-vlcek/bigdesk](http://github.com/lukas-vlcek/bigdesk) and
> > 
> > # [http://mobz.github.com/elasticsearch-head](http://mobz.github.com/elasticsearch-head) to inspect the cluster
> > 
> > state.
> > 
> > # A node can have generic attributes associated with it, which can later
> > 
> > be used
> > 
> > # for customized shard allocation filtering, or allocation awareness. An
> > 
> > attribute
> > 
> > # is a simple key value pair, similar to node.key: value, here is an
> > 
> > example:
> > 
> > # 
> > 
> > # node.rack: rack314
> > 
> > # 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
> > 
> > #################################### Index  
> > ####################################
> > 
> > # You can set a number of options (such as shard/replica options, mapping
> > 
> > # or analyzer definitions, translog settings, ...) for indices globally,
> > 
> > # in this file.
> > 
> > # 
> > 
> > # Note, that it makes more sense to configure index settings specifically
> > 
> > for
> > 
> > # a certain index, either when creating it or by using the index
> > 
> > templates API.
> > 
> > # 
> > 
> > # See \<
> > 
> > [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://elasticsearch.org/guide/en/elasticsearch/reference/current/index-modules.html)\>  
> > and
> > 
> > # \<
> > 
> > [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://elasticsearch.org/guide/en/elasticsearch/reference/current/indices-create-index.html)
> > 
> > > 
> > 
> > # for more information.
> > 
> > # Set the number of shards (splits) of an index (5 by default):
> > 
> > # 
> > 
> > # index.number\_of\_shards: 5
> > 
> > # Set the number of replicas (additional copies) of an index (1 by
> > 
> > default):
> > 
> > # 
> > 
> > # index.number\_of\_replicas: 1
> > 
> > # Note, that for development on a local machine, with small indices, it
> > 
> > usually
> > 
> > # makes sense to "disable" the distributed features:
> > 
> > # 
> > 
> > # index.number\_of\_shards: 1
> > 
> > # index.number\_of\_replicas: 0
> > 
> > # These settings directly affect the performance of index and search
> > 
> > operations
> > 
> > # in your cluster. Assuming you have enough machines to hold shards and
> > 
> > # replicas, the rule of thumb is:
> > 
> > # 
> > 
> > # 1. Having more _shards_ enhances the _indexing_ performance and allows
> > 
> > to
> > 
> > # _distribute_ a big index across machines.
> > 
> > # 2. Having more _replicas_ enhances the _search_ performance and
> > 
> > improves the
> > 
> > # cluster _availability_.
> > 
> > # 
> > 
> > # The "number\_of\_shards" is a one-time setting for an index.
> > 
> > # 
> > 
> > # The "number\_of\_replicas" can be increased or decreased anytime,
> > 
> > # by using the Index Update Settings API.
> > 
> > # 
> > 
> > # Elasticsearch takes care about load balancing, relocating, gathering the
> > 
> > # results from nodes, etc. Experiment with different settings to fine-tune
> > 
> > # your setup.
> > 
> > # Use the Index Status API ([http://localhost:9200/A/\_status](http://localhost:9200/A/_status)) to inspect
> > 
> > # the index status.
> > 
> > #################################### Paths  
> > ####################################
> > 
> > # Path to directory containing configuration (this file and logging.yml):
> > 
> > # 
> > 
> > # path.conf: /path/to/conf
> > 
> > # Path to directory where to store index data allocated for this node.
> > 
> > # 
> > 
> > # path.data: /path/to/data
> > 
> > # 
> > 
> > # Can optionally include more than one location, causing data to be
> > 
> > striped across
> > 
> > # the locations (a la RAID 0) on a file level, favouring locations with
> > 
> > most free
> > 
> > # space on creation. For example:
> > 
> > # 
> > 
> > # path.data: /path/to/data1,/path/to/data2
> > 
> > # Path to temporary files:
> > 
> > # 
> > 
> > # path.work: /path/to/work
> > 
> > # Path to log files:
> > 
> > # 
> > 
> > # path.logs: /path/to/logs
> > 
> > # Path to where plugins are installed:
> > 
> > # 
> > 
> > # path.plugins: /path/to/plugins
> > 
> > #################################### Plugin  
> > ###################################
> > 
> > # If a plugin listed here is not installed for current node, the node
> > 
> > will not start.
> > 
> > # 
> > 
> > # plugin.mandatory: mapper-attachments,lang-groovy
> > 
> > ################################### Memory  
> > ####################################
> > 
> > # Elasticsearch performs poorly when JVM starts swapping: you should
> > 
> > ensure that
> > 
> > # it _never_ swaps.
> > 
> > # 
> > 
> > # Set this property to true to lock the memory:
> > 
> > # 
> > 
> > # bootstrap.mlockall: true
> > 
> > # Make sure that the ES\_MIN\_MEM and ES\_MAX\_MEM environment variables are
> > 
> > set
> > 
> > # to the same value, and that the machine has enough memory to allocate
> > 
> > # for Elasticsearch, leaving enough memory for the operating system
> > 
> > itself.
> > 
> > # 
> > 
> > # You should also make sure that the Elasticsearch process is allowed to
> > 
> > lock
> > 
> > # the memory, eg. by using `ulimit -l unlimited`.
> > 
> > ############################## Network And HTTP  
> > ###############################
> > 
> > # Elasticsearch, by default, binds itself to the 0.0.0.0 address, and
> > 
> > listens
> > 
> > # on port [9200-9300] for HTTP traffic and on port [9300-9400] for
> > 
> > node-to-node
> > 
> > # communication. (the range means that if the port is busy, it will
> > 
> > automatically
> > 
> > # try the next port).
> > 
> > # Set the bind address specifically (IPv4 or IPv6):
> > 
> > # 
> > 
> > # network.bind\_host: 192.168.0.1
> > 
> > # Set the address other nodes will use to communicate with this node. If
> > 
> > not
> > 
> > # set, it is automatically derived. It must point to an actual IP address.
> > 
> > # 
> > 
> > # network.publish\_host: 192.168.0.1
> > 
> > # Set both 'bind\_host' and 'publish\_host':
> > 
> > # 
> > 
> > # network.host: 192.168.0.1
> > 
> > # Set a custom port for the node to node communication (9300 by default):
> > 
> > # 
> > 
> > # transport.tcp.port: 9300
> > 
> > # Enable compression for all communication between nodes (disabled by
> > 
> > default):
> > 
> > # 
> > 
> > # transport.tcp.compress: true
> > 
> > # Set a custom port to listen for HTTP traffic:
> > 
> > # 
> > 
> > # http.port: 9200
> > 
> > # Set a custom allowed content length:
> > 
> > # 
> > 
> > # http.max\_content\_length: 100mb
> > 
> > # Disable HTTP completely:
> > 
> > # 
> > 
> > # http.enabled: false
> > 
> > ################################### Gateway  
> > ###################################
> > 
> > # The gateway allows for persisting the cluster state between full cluster
> > 
> > # restarts. Every change to the state (such as adding an index) will be
> > 
> > stored
> > 
> > # in the gateway, and when the cluster starts up for the first time,
> > 
> > # it will read its state from the gateway.
> > 
> > # There are several types of gateway implementations. For more
> > 
> > information, see
> > 
> > # \<
> > 
> > [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://elasticsearch.org/guide/en/elasticsearch/reference/current/modules-gateway.html)
> > 
> > > .
> > 
> > # The default gateway type is the "local" gateway (recommended):
> > 
> > # 
> > 
> > # gateway.type: local
> > 
> > # Settings below control how and when to start the initial recovery
> > 
> > process on
> > 
> > # a full cluster restart (to reuse as much local data as possible when
> > 
> > using shared
> > 
> > # gateway).
> > 
> > # Allow recovery process after N nodes in a cluster are up:
> > 
> > # 
> > 
> > # gateway.recover\_after\_nodes: 1
> > 
> > # Set the timeout to initiate the recovery process, once the N nodes
> > 
> > # from previous setting are up (accepts time value):
> > 
> > # 
> > 
> > # gateway.recover\_after\_time: 5m
> > 
> > # Set how many nodes are expected in this cluster. Once these N nodes
> > 
> > # are up (and recover\_after\_nodes is met), begin recovery process
> > 
> > immediately
> > 
> > # (without waiting for recover\_after\_time to expire):
> > 
> > # 
> > 
> > # gateway.expected\_nodes: 2
> > 
> > ############################# Recovery Throttling  
> > #############################
> > 
> > # These settings allow to control the process of shards allocation between
> > 
> > # nodes during initial recovery, replica allocation, rebalancing,
> > 
> > # or when adding and removing nodes.
> > 
> > # Set the number of concurrent recoveries happening on a node:
> > 
> > # 
> > 
> > # 1. During the initial recovery
> > 
> > # 
> > 
> > # cluster.routing.allocation.node\_initial\_primaries\_recoveries: 4
> > 
> > # 
> > 
> > # 2. During adding/removing nodes, rebalancing, etc
> > 
> > # 
> > 
> > # cluster.routing.allocation.node\_concurrent\_recoveries: 2
> > 
> > # Set to throttle throughput when recovering (eg. 100mb, by default 20mb):
> > 
> > # 
> > 
> > # indices.recovery.max\_bytes\_per\_sec: 20mb
> > 
> > # Set to limit the number of open concurrent streams when
> > 
> > # recovering a shard from a peer:
> > 
> > # 
> > 
> > # indices.recovery.concurrent\_streams: 5
> > 
> > ################################## Discovery  
> > ##################################
> > 
> > # Discovery infrastructure ensures nodes can be found within a cluster
> > 
> > # 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. Its recommended to set it to a higher
> > 
> > value
> > 
> > # than 1 when running more than 2 nodes in the cluster.
> > 
> > # 
> > 
> > # discovery.zen.minimum\_master\_nodes: 1
> > 
> > # 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
> > 
> > # to minimize discovery failures:
> > 
> > # 
> > 
> > # discovery.zen.ping.timeout: 3s
> > 
> > # For more information, see
> > 
> > # \<
> > 
> > [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://elasticsearch.org/guide/en/elasticsearch/reference/current/modules-discovery-zen.html)
> > 
> > > 
> > 
> > # Unicast discovery allows to explicitly control which nodes will be used
> > 
> > # to discover the cluster. It can be used when multicast is not present,
> > 
> > # or to restrict the cluster communication-wise.
> > 
> > # 
> > 
> > # 1. Disable multicast discovery (enabled by default):
> > 
> > # 
> > 
> > # 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: ["10.0.0.4", "10.0.0.5", "10.0.0.6"]
> > 
> > # EC2 discovery allows to use AWS EC2 API in order to perform discovery.
> > 
> > # 
> > 
> > # You have to install the cloud-aws plugin for enabling the EC2 discovery.
> > 
> > # 
> > 
> > # For more information, see
> > 
> > # \<
> > 
> > [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://elasticsearch.org/guide/en/elasticsearch/reference/current/modules-discovery-ec2.html)
> > 
> > > 
> > 
> > # 
> > 
> > # See [http://elasticsearch.org/tutorials/elasticsearch-on-ec2/](http://elasticsearch.org/tutorials/elasticsearch-on-ec2/)
> > 
> > # for a step-by-step tutorial.
> > 
> > ################################## Slow Log  
> > ##################################
> > 
> > # Shard level query and fetch threshold logging.
> > 
> > #index.search.slowlog.threshold.query.warn: 10s  
> > #index.search.slowlog.threshold.query.info: 5s  
> > #index.search.slowlog.threshold.query.debug: 2s  
> > #index.search.slowlog.threshold.query.trace: 500ms  
> > #index.search.slowlog.threshold.fetch.warn: 1s  
> > #index.search.slowlog.threshold.fetch.info: 800ms  
> > #index.search.slowlog.threshold.fetch.debug: 500ms  
> > #index.search.slowlog.threshold.fetch.trace: 200ms  
> > #index.indexing.slowlog.threshold.index.warn: 10s  
> > #index.indexing.slowlog.threshold.index.info: 5s  
> > #index.indexing.slowlog.threshold.index.debug: 2s  
> > #index.indexing.slowlog.threshold.index.trace: 500ms  
> > ################################## GC Logging  
> > ################################  
> > #monitor.jvm.gc.young.warn: 1000ms  
> > #monitor.jvm.gc.young.info: 700ms  
> > #monitor.jvm.gc.young.debug: 400ms  
> > #monitor.jvm.gc.old.warn: 10s  
> > #monitor.jvm.gc.old.info: 5s  
> > #monitor.jvm.gc.old.debug: 2s  
> > ################################# AZURE PLUGIN  
> > ###############################  
> > cloud:  
> > azure:  
> > keystore: c:/Certs/certificate.pfx  
> > password: password  
> > subscription\_id: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx  
> > service\_name: apw-es-vms  
> > discovery:  
> > type: azure
> > 
> > Cluster 2 - brand new clean cluster with same base configuration and only  
> > differences in elasticsearch.yml file are subscription id, service name and  
> > cluster name. Once again none of the nodes in this configuration can see  
> > each other.
> > 
> > I suspect this is a configuration issue but my experience with  
> > elasticsearch is limited. Does anyone have any ideas what I could have  
> > configured incorrectly?
> > 
> > Thanks
> > 
> > ## Andrew
> > 
> > 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 [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com).  
> > To view this discussion on the web visit  
> > [https://groups.google.com/d/msgid/elasticsearch/12cca085-c7db-440e-8740-0bb973ff68a5%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/12cca085-c7db-440e-8740-0bb973ff68a5%40googlegroups.com)  
> > .  
> > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).
> 
> --  
> 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 [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com) \<javascript:\>.  
> To view this discussion on the web visit  
> [https://groups.google.com/d/msgid/elasticsearch/f322a3b4-733f-4718-a051-0654e4d38ab2%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/f322a3b4-733f-4718-a051-0654e4d38ab2%40googlegroups.com)  
> .  
> For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

--  
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 [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/37603911-6d7f-4351-b47d-b80f5014a11f%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/37603911-6d7f-4351-b47d-b80f5014a11f%40googlegroups.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 6, 2017, 1:52am UTC](https://discuss.elastic.co/t/azure-cloud-plugin-problems/15600/6 "2017-07-06T01:52:29Z")

</div>