EC2 VPC Discovery Issues

Elastic Stack Elasticsearch
1

Hi Guys,

I've recently spun up a new ES cluster (2 nodes) to replace my old stack.
The new cluster is using the newest ES version (0.20.4) and newest AWS
plugin (1.10.0) and is backing to S3. I cannot get them to talk to each
other now and it's making me crazy. I'm using two Ubuntu 12.04 EC2
instances inside of a VPC. The nodes are in the same region, zone and
subnet and the security groups for both the LB and EC2 instances both have
9200 and 9300 open to the world.

Here is a copy of their config files:

------- NODE 1 -------

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

cluster.name: wtrsearch
node.name: node1

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

index.number_of_shards: 6
index.number_of_replicas: 1

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

path.data: /usr/local/var/data/elasticsearch
path.logs: /usr/local/var/log/elasticsearch

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

bootstrap.mlockall: true

################################## Discovery
##################################
discovery.type: ec2
discovery.ec2.availability_zones: us-west-1a
discovery.ec2.ping_timeout: 30s
discovery.ec2.tag: wtrsearch_production

cloud.node.auto_attributes: true
cloud.aws.region: us-west-1
cloud.aws.access_key: [omitted]
cloud.aws.secret_key: [omitted]

################################## Persistence
##################################
gateway.type: s3
gateway.s3.bucket: wtr-search-data-us-west-1-test

------- NODE 2 -------

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

cluster.name: wtrsearch
node.name: node2

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

index.number_of_shards: 6
index.number_of_replicas: 1

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

path.data: /usr/local/var/data/elasticsearch
path.logs: /usr/local/var/log/elasticsearch

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

bootstrap.mlockall: true

################################## Discovery
##################################
discovery.type: ec2
discovery.ec2.availability_zones: us-west-1a
discovery.ec2.ping_timeout: 30s
discovery.ec2.tag: wtrsearch_production

cloud.node.auto_attributes: true
cloud.aws.region: us-west-1
cloud.aws.access_key: [omitted]
cloud.aws.secret_key: [omitted]

################################## Persistence
##################################
gateway.type: s3
gateway.s3.bucket: wtr-search-data-us-west-1-test

Can anyone think of any reason why these two wouldn't be able to talk to
one another? I'm absolutely pulling my hair out.

They both have cluster health outputs that look like this:

{

  • cluster_name: wtr_search_production
  • status: green
  • timed_out: false
  • number_of_nodes: 1
  • number_of_data_nodes: 1
  • active_primary_shards: 0
  • active_shards: 0
  • relocating_shards: 0
  • initializing_shards: 0
  • unassigned_shards: 0

}

They both have cluster state outputs that look like this:

{

  • cluster_name: wtr_search_production
  • master_node: HPscfXXMQNqSIuXA3b6MLQ
  • blocks: { }
  • nodes: {
    • HPscfXXMQNqSIuXA3b6MLQ: {
      • name: wtr-search-watchtower-i-70776729
      • transport_address: inet[/10.200.60.18:9300]
      • attributes: {
        • aws_availability_zone: us-west-1a
          }
          }
          }
  • metadata: {
    • templates: { }
    • indices: { }
      }
  • routing_table: {
    • indices: { }
      }
  • routing_nodes: {
    • unassigned: [ ]
    • nodes: {
      • HPscfXXMQNqSIuXA3b6MLQ: [ ]
        }
        }
  • allocations: [ ]

}

Except with (obviously) different addresses, names and master nodes.

Please help!

Thanks!

--
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.
For more options, visit https://groups.google.com/groups/opt_out.