A bit more on this. In the end I added: elasticsearch_network_host = <hostname or ip of node> The default for that is to bind to loopback, which causes a problem because (I guess) because it doesnt allow the graylog elasticsearch node to talk to the other graylog elasticsearch nodes.
They don't clash with the existing cluster because the graylog elasticsearch node listens on 9350, not 9300. Now all three graylog nodes are talking to the three node elasticsearch cluster, as required. On Friday, 9 December 2016 13:49:45 UTC, Jochen Schalanda wrote: > > Hi Dylan, > > On Friday, 9 December 2016 13:51:11 UTC+1, Dylan Humphreys wrote: >> >> elasticsearch_discovery_zen_ping_unicast_hosts >> >> Actually does, if (as it appears) its not for pointing graylog at the >> address(es) of the elasticsearch cluster. >> > > That is exactly what this setting is for. See > https://www.elastic.co/guide/en/elasticsearch/reference/2.4/modules-discovery-zen.html > > for details in the Elasticsearch documentation. > > Cheers, > Jochen > -- You received this message because you are subscribed to the Google Groups "Graylog Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to graylog2+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/graylog2/1bbac6e2-3bf7-40b7-93dc-7b2ef629264e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
