* David Pilato <[email protected]> [2014-04-11 06:51:56]:
> Sorry Matt
>
>
> I did not get a chance to look at it yet in details.
> Just to make sure it's not related to the jetty plugin, could you try remove
> it from the tribe node?
I just pared back the config on the tribe node to just the minimum, (gist
updated), and it still occurs. I tried increasing the logging and I see
things like:
[2014-04-11 11:59:08,379][DEBUG][transport.netty ]
[es-tribe-01/sydney] disconnected from
[[#zen_unicast_1#][es-tribe-01][inet[/54.206.x.x:9300]]]
[2014-04-11 11:59:08,381][DEBUG][transport.netty ]
[es-tribe-01/sydney] disconnected from
[[#zen_unicast_2#][es-tribe-01][inet[/54.206.x.x:9300]]]
[2014-04-11 11:59:08,382][DEBUG][discovery.zen ]
[es-tribe-01/sydney] filtered ping responses: (filter_client[true],
filter_data[false])
--> target
[[es-master-02][4rcZQu2USJuk6sSGu-by0w][es-master-02][inet[/172.31.x.x:9300]]{aws_availability_zone=ap-southeast-2b,
data=false, master=true}], master
[[es-master-02][4rcZQu2USJuk6sSGu-by0w][es-master-02][inet[/172.31.x.x:9300]]{aws_availability_zone=ap-southeast-2b,
data=false, master=true}]
--> target
[[es-master-01][whb9bzt_QV2AyiuhIyBtWw][es-master-01][inet[/172.31.x.x:9300]]{aws_availability_zone=ap-southeast-2a,
data=false, master=true}], master
[[es-master-02][4rcZQu2USJuk6sSGu-by0w][es-master-02][inet[/172.31.x.x:9300]]{aws_availability_zone=ap-southeast-2b,
data=false, master=true}]
I would expect the inet[/172.31.x.x:9300]'s to actually be
inet[ec2-54-206-x-x.ap-southeast-2.compute.amazonaws.com/172.31.x.x:9300]
which I see for some of the nodes when I query the cluster using the
/_nodes/transport endpoint.
Every node with HTTP enabled reports its http_adddress with the EC2 DNS
name included, but only the node I make the request to reports its
publish_address with the DNS included, all other nodes just contain
their IP address, e.g.:
# curl -s http://elb:9200/_nodes/transport?pretty | grep http_address
"http_address" :
"inet[ec2-54-206-x-x.ap-southeast-2.compute.amazonaws.com/172.31.x.x:9200]",
"http_address" :
"inet[ec2-54-206-x-x.ap-southeast-2.compute.amazonaws.com/172.31.x.x:9200]",
# curl -s http://elb:9200/_nodes/transport?pretty | grep publish_address
"publish_address" : "inet[/172.31.x.x:9300]"
"publish_address" : "inet[/172.31.x.x:9300]"
"publish_address" : "inet[/172.31.x.x:9300]"
"publish_address" :
"inet[ec2-54-206-x-x.ap-southeast-2.compute.amazonaws.com/172.31.x.x:9300]"
"publish_address" : "inet[/172.31.x.x:9300]"
"publish_address" : "inet[/172.31.x.x:9300]"
(There's six nodes in the cluster but only two have HTTP enabled)
I would expect all publish_addresses to contain the DNS name.
> Is the tribe node sharing the same security group?
The tribe node is not actually in EC2 at all, but the security groups
are set so it has full access on ports 9300-9399 to each node, which I
guess is confirmed by the fact its getting as far as the list of masters
with their private IP addresses via the zen unicast hosts.
Matt
--
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/20140411115608.GB2245%40simulant.bodgit-n-scarper.com.
For more options, visit https://groups.google.com/d/optout.
