Hi,

I've deployed a two nodes ElasticSearch cluster on Windows Azure. My setup 
is the following :

   - I use OpenSSL 1.0.1c (as recommended on the plugin's GitHub pahe, 
   other versions gave me trouble) to generate the SSH key, certificate and 
   pkcs12 keystore
   - the Azure plugin (2.2.0) is installed on both nodes and defined as 
   mandatory in elasticsearch.yml
   - the VMs run Ubuntu 12.04 (the exact image id is 
   
*b39f27a8b8c64d52b05eac6a62ebad85__Ubuntu-12_04_4-LTS-amd64-server-20140514-en-us-30GB*
   )

When I start the cluster I have the split brain syndrome, each node elects 
itself as master and fails to see the other one. I configured the discovery 
log level to TRACE to get more detailed information, and there is the 
following error message :

[2014-05-26 17:46:21,285][WARN ][cloud.azure              ] [elasticpoc1] 
can not get list of azure nodes: Server returned HTTP response code: 403 
for URL: 
https://management.core.windows.net/1d4c95fb-d9f1-4594-af6b-bfd3941f1c64/services/hostedservices/elasticpoc?embed-detail=true

This error appears 3 times in the log before the local node is elected as 
master. 

I've attached the logs from both my nodes, as well as the 
*elasticsearch.yml* config file (which only differs by setting a distinct 
node name between the 2 nodes).

I'm pretty clueless as to how I should proceed to get this right, so any 
help would be much appreciated.

Best regards,

Nicolas

-- 
You received this message because you are subscribed to the Google Groups 
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/elasticsearch/39ed88e3-c30c-428a-a65f-c76cfbf99ec2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Attachment: elasticpoc1.log
Description: Binary data

Attachment: elasticpoc2.log
Description: Binary data

Attachment: elasticsearch.yml
Description: Binary data

Reply via email to