Adding third node from subnet

Elastic Stack Elasticsearch
1

Hi, I have a cluster on the same subnet that works

VM1
cluster.name: NCA-CLUSTER
node.name: logwarehouse_master1
network.host: 192.168.18.15
discovery.zen.ping.unicast.hosts: ["192.168.18.18:9300", "172.16.207.33:9300"]

VM2
cluster.name: NCA-CLUSTER
node.name: logwarehouse_master2
network.host: 192.168.18.18
discovery.zen.ping.unicast.hosts: ["192.168.18.15:9300", "172.16.207.33:9300"]

This cluster works. I prepared a third VM on another subnet, and I can't connect it to my cluster

VM3
cluster.name: NCA-CLUSTER
node.name: logwarehouse_data1
network.host: 172.16.207.33
discovery.zen.ping.unicast.hosts: ["192.168.18.15:9300", "192.168.18.18:9300"]

Telnet works on 192.168.18.15 9300 and for 192.168.18.18 9300
Telnet works for 172.16.207.33 9300 for 192.168.18.15 and 192.168.18.18

I donn't know what I must add for my cluster to work

Thank you for your help

2

Hi, can you provide your master logs ?

3

What about telnet from 192.168 to 172.16?

4

Hi. It works, that's why I don't underdtand why third node won't connect

Envoyé de mon iPhone

5

Do you have this properties:

discovery.zen.ping.multicast.enabled: false

EDIT: if version < 5.0

6

I have this line in my elastic.yml but it is not active.

discovery.zen.ping.multicast.enabled: false

7

Are these in the same datacentre/location?

8

can you provide log of your VM3 ? /var/log/elasticsearch/*.log

9

Hi, yes they are on the same Datacentre

10

And the elasticsearch logs are empty. On /var/log/elasticsearch/ I have an elastic.log but it is empty

11

I found that information in a new log file :

[logwarehouse_data1] initialized
[2017-01-09T11:01:26,995][INFO ][o.e.n.Node ] [logwarehouse_data1] starting ...
[2017-01-09T11:01:27,209][INFO ][o.e.t.TransportService ] [logwarehouse_data1] publish_address {172.16.207.33:9300}, bound_addresses {172.16.207.33:9300}
[2017-01-09T11:01:27,214][INFO ][o.e.b.BootstrapCheck ] [logwarehouse_data1] bound or publishing to a non-loopback or non-link-local address, enforcing bootstrap checks
[2017-01-09T11:01:27,450][WARN ][o.e.d.z.UnicastZenPing ] [logwarehouse_data1] [1] failed send ping to {#zen_unicast_1#}{wqGH5S7qSamfkLQ2QDmMOQ}{192.168.18.15}{192.168.18.15:9300}
java.lang.IllegalStateException: handshake failed with {#zen_unicast_1#}{wqGH5S7qSamfkLQ2QDmMOQ}{192.168.18.15}{192.168.18.15:9300}
at org.elasticsearch.transport.TransportService.handshake(TransportService.java:370) ~[elasticsearch-5.1.1.jar:5.1.1]
at org.elasticsearch.transport.TransportService.connectToNodeLightAndHandshake(TransportService.java:345) ~[elasticsearch-5.1.1.jar:5.1.1]
at org.elasticsearch.transport.TransportService.connectToNodeLightAndHandshake(TransportService.java:319) ~[elasticsearch-5.1.1.jar:5.1.1]
at org.elasticsearch.discovery.zen.UnicastZenPing$2.run(UnicastZenPing.java:473) [elasticsearch-5.1.1.jar:5.1.1]
at org.elasticsearch.common.util.concurrent.ThreadContext$ContextPreservingRunnable.run(ThreadContext.java:458) [elasticsearch-5.1.1.jar:5.1.1]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [?:1.8.0_111]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [?:1.8.0_111]
at java.lang.Thread.run(Thread.java:745) [?:1.8.0_111]
Caused by: org.elasticsearch.transport.RemoteTransportException: [logwarehouse_master1][192.168.18.15:9300][internal:transport/handshake]
Caused by: org.elasticsearch.ElasticsearchSecurityException: failed to verify signed authentication information

12

But:

Are your certain that you can telnet from VM3 (172.16.207.33) to 2 others VM using the 9300 port ?

13

Yes it works :

root@vmnt2042tech:~>telnet 192.168.18.15 9300
Trying 192.168.18.15...
Connected to 192.168.18.15.
Escape character is '^]'.

root@vmnt2042tech:~>telnet 192.168.18.18 9300
Trying 192.168.18.18...
Connected to 192.168.18.18.
Escape character is '^]'.

14

Another question : VM3 use the same ES version that VM1 & VM2 ?

15

Yes, same version.

But I found something : VM3 don't use the system_key file generated by VM1.
The authentification problem may comes from that

16

The problem is resolved.

In VM3, the file system_key in /etc/elasticsearch/x-pack was corrupted (I don't know why...)
In VM1 I generate a new system_key and I send it on VM3 with the terminal.

Thanks for all your help, I really appreciate.

Fayce

1 Like
17

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