AWS Cloud Plugin


#1

Hello,

AWS Cloud Plugin doesn't seem to work with 2.1.0. Here's details ...

On first node ...

{code}
es@ip-10-4-148-190:~$ /data/es/elasticsearch-2.1.0/bin/elasticsearch \

-Dcluster.name=nagabhu
-Dnode.name=$HOSTNAME -Dnetwork.host=ec2
-Ddiscovery.type=ec2 -Dcloud.aws.region=us-west-2
[2015-12-15 01:54:07,247][INFO ][node ] [ip-10-4-148-190] version[2.1.0], pid[6753], build[72cd1f1/2015-11-18T22:40:03Z]
[2015-12-15 01:54:07,247][INFO ][node ] [ip-10-4-148-190] initializing ...
[2015-12-15 01:54:07,508][INFO ][plugins ] [ip-10-4-148-190] loaded [cloud-aws], sites []
[2015-12-15 01:54:07,527][INFO ][env ] [ip-10-4-148-190] using [1] data paths, mounts [[/data (/dev/md0)]], net usable_space [5.1tb], net total_space [5.4tb], spins? [possibly], types [ext4]
[2015-12-15 01:54:09,755][INFO ][node ] [ip-10-4-148-190] initialized
[2015-12-15 01:54:09,755][INFO ][node ] [ip-10-4-148-190] starting ...
[2015-12-15 01:54:09,836][INFO ][transport ] [ip-10-4-148-190] publish_address {10.4.148.190:9300}, bound_addresses {10.4.148.190:9300}
[2015-12-15 01:54:09,845][INFO ][discovery ] [ip-10-4-148-190] nagabhu/m6qrvXnoSdGJTXy51abfjQ
[2015-12-15 01:54:15,453][INFO ][cluster.service ] [ip-10-4-148-190] new_master {ip-10-4-148-190}{m6qrvXnoSdGJTXy51abfjQ}{10.4.148.190}{10.4.148.190:9300}, reason: zen-disco-join(elected_as_master, [0] joins received)
[2015-12-15 01:54:15,467][INFO ][http ] [ip-10-4-148-190] publish_address {10.4.148.190:9200}, bound_addresses {10.4.148.190:9200}
[2015-12-15 01:54:15,468][INFO ][node ] [ip-10-4-148-190] started
[2015-12-15 01:54:15,499][INFO ][gateway ] [ip-10-4-148-190] recovered [0] indices into cluster_state
{code}

On second node ...

{code}
es@ip-10-4-148-191:~$ /data/es/elasticsearch-2.1.0/bin/elasticsearch \

-Dcluster.name=nagabhu
-Dnode.name=$HOSTNAME -Dnetwork.host=ec2
-Ddiscovery.type=ec2 -Dcloud.aws.region=us-west-2
[2015-12-15 01:58:41,636][INFO ][node ] [ip-10-4-148-191] version[2.1.0], pid[6459], build[72cd1f1/2015-11-18T22:40:03Z]
[2015-12-15 01:58:41,636][INFO ][node ] [ip-10-4-148-191] initializing ...
[2015-12-15 01:58:41,871][INFO ][plugins ] [ip-10-4-148-191] loaded [cloud-aws], sites []
[2015-12-15 01:58:41,891][INFO ][env ] [ip-10-4-148-191] using [1] data paths, mounts [[/data (/dev/md0)]], net usable_space [5.1tb], net total_space [5.4tb], spins? [possibly], types [ext4]
[2015-12-15 01:58:44,113][INFO ][node ] [ip-10-4-148-191] initialized
[2015-12-15 01:58:44,113][INFO ][node ] [ip-10-4-148-191] starting ...
[2015-12-15 01:58:44,198][INFO ][transport ] [ip-10-4-148-191] publish_address {10.4.148.191:9300}, bound_addresses {10.4.148.191:9300}
[2015-12-15 01:58:44,205][INFO ][discovery ] [ip-10-4-148-191] nagabhu/4EgzisuSRDCMZzgUCA7fJA
[2015-12-15 01:58:49,556][INFO ][cluster.service ] [ip-10-4-148-191] new_master {ip-10-4-148-191}{4EgzisuSRDCMZzgUCA7fJA}{10.4.148.191}{10.4.148.191:9300}, reason: zen-disco-join(elected_as_master, [0] joins received)
[2015-12-15 01:58:49,570][INFO ][http ] [ip-10-4-148-191] publish_address {10.4.148.191:9200}, bound_addresses {10.4.148.191:9200}
[2015-12-15 01:58:49,570][INFO ][node ] [ip-10-4-148-191] started
[2015-12-15 01:58:49,608][INFO ][gateway ] [ip-10-4-148-191] recovered [0] indices into cluster_state
{code}

Here's the issue ... Only one node shows up ...

{code}

curl 10.4.148.190:9200/_nodes?pretty 2>/dev/null | grep trans.*addr
"transport_address" : "10.4.148.190:9300",
{code}


#2

Please ignore. The issue is related to a variance between our Dev and Prod environments. Works fine in Prod, but fails in Dev, so obviously our environment/network setup/configuration issue.


(system) #3