Hi I am trying to create a cluster that is secured on a number of raspberry
pi's. If I start just one node with the following config I get a timeout to
that same node. So it is trying to ping itself and that does not work. Any
ideas?
Config:
cluster.name: jc-mypi
node.name: jc-pi-red
marvel.agent.indices: my*
marvel.agent.interval: 10s
marvel.agent.enabled: false
shield.audit.enabled: true
shield.ssl.keystore.path: /etc/elasticsearch/jcpi.jks
shield.ssl.keystore.password: geheim
shield.transport.ssl: true
discovery.zen.ping.multicast.enabled: false
discovery.zen.ping.unicast.hosts: ["192.168.1.11:9300", "192.168.1.12:9300"]
In the log:
[2015-02-12 21:36:40,078][WARN ][shield.transport ] [jc-pi-red]
Received response for a request that has timed out, sent [21455ms] ago,
timed out [17704ms] ago, action [internal:discovery/zen/unicast], node
[[jc-pi-red][o4b8he9qQFiSzBV3ckkF1Q][jc-pi-red][inet[192.168.1.10/192.168.1.10:9300]]],
id [0]
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/791792bc-9ee3-48ca-9f61-e2bd71952cc9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
As pointed out by Jay Modi when discussing another question I had, this is
a timeout issue. The pi's do not have a lot of processing power and adding
ssl is to heavy for the pi. Upgrading the timeout to 30 seconds did help.
On Thu, Feb 12, 2015 at 9:41 PM, Jettro Coenradie <
jettro.coenradie@gmail.com> wrote:
Hi I am trying to create a cluster that is secured on a number of
raspberry pi's. If I start just one node with the following config I get a
timeout to that same node. So it is trying to ping itself and that does not
work. Any ideas?
Config:
cluster.name: jc-mypi
node.name: jc-pi-red
marvel.agent.indices: my*
marvel.agent.interval: 10s
marvel.agent.enabled: false
shield.audit.enabled: true
shield.ssl.keystore.path: /etc/elasticsearch/jcpi.jks
shield.ssl.keystore.password: geheim
shield.transport.ssl: true
discovery.zen.ping.multicast.enabled: false
discovery.zen.ping.unicast.hosts: ["192.168.1.11:9300", "192.168.1.12:9300
"]
In the log:
[2015-02-12 21:36:40,078][WARN ][shield.transport ] [jc-pi-red]
Received response for a request that has timed out, sent [21455ms] ago,
timed out [17704ms] ago, action [internal:discovery/zen/unicast], node
[[jc-pi-red][o4b8he9qQFiSzBV3ckkF1Q][jc-pi-red][inet[
192.168.1.10/192.168.1.10:9300]]
http://192.168.1.10/192.168.1.10:9300]]], id [0]
Thanks
--
You received this message because you are subscribed to a topic in the
Google Groups "elasticsearch" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/elasticsearch/9B3K7_J-hCg/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/791792bc-9ee3-48ca-9f61-e2bd71952cc9%40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/791792bc-9ee3-48ca-9f61-e2bd71952cc9%40googlegroups.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.
--
Jettro Coenradie
--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CABB4caPD3X9U9A%3DT_JirRA5nocanu-WfarJU6X%2BepHyLj0i5UA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.