ES cluster with Docker in AWS env


(K Zk93) #1

Hello guys,

I would like to require your help on the setup of my elasticsearch cluster (ES 5.0) using docker in an AWS cloud.

I've been trying to do it using the zen.discovery mode AND ec2.discovery mode, both of them as a failure.

At this point, I got 2 instances that are able to communicate each other (I can curl instance2 elastic with instance1 as an exemple) + when I'm looking at logs I got this.

new_master {db21a49186b9}{WBEHmV4zQkeufwtCMNXbSg}{GgNxTf-QQgWillGXfD79gg}{172.17.0.3}{172.17.0.3:9300}, reason: zen-disco-elected-as-master ([0] nodes joined)

Here instance1 is elected as master (which is normal since it has node.master: true

But on instance2 I got this log

failed to send join request to master [{db21a49186b9}{WBEHmV4zQkeufwtCMNXbSg}{GgNxTf-QQgWillGXfD79gg}{172.17.0.3}{172.17.0.3:9300}], reason [RemoteTransportException[[4e2c0e8258ea][172.17.0.3:9300][internal:discovery/zen/join]]; nested: NotMasterException[Node [{4e2c0e8258ea}{TrEuGtRNST6wnZjIXdJmWw}{lipkjQKFRnCwgQAtM5LImg}{172.17.0.3}{172.17.0.3:9300}] not master for join request]; ], tried [3] times

It looks like there are able to communicate each other, slave is able to recognize master (since the hostname match) but it cannot join him.

Here is my YML:

network.host: site
discovery.zen.ping_timeout: 30s
discovery.zen.ping.unicast.hosts: ["172.31.9.125", "172.31.9.124"] (both private IP of my instances, both in the same subnet)
script.engine.javascript.inline.search: on
node.master: ${MASTER}

Thank you very much guys :slight_smile:


(system) #2

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.