Hi Nathan, the two configuration settings you've mentioned, elasticsearch_discovery_zen_ping_multicast_enabled and elasticsearch_discovery_zen_ping_unicast_hosts, are from the Graylog configuration file and don't need to be changed when adding another Elasticsearch node.
Simply make sure, that the new Elasticsearch node has the same cluster name, can connect to all other Elasticsearch nodes (including Graylog itself), and has a list of the other Elasticsearch nodes to connect to. See http://docs.graylog.org/en/2.0/pages/configuration/elasticsearch.html#configuration for further details. Cheers, Jochen On Thursday, 28 July 2016 16:52:16 UTC+2, Nathan Mace wrote: > > I just installed Graylog + Mongo DB + Elastic Search on a Cent OS VM, > following the Graylog official documentation. Working great. > > However, when the time comes that it isn't feasible to add additional CPU > and RAM to the VM and I need to add another Elastic Search Node, what is > the procedure for doing that to an existing "cluster" (even if that > existing cluster is a single VM). > > I think it would be something along these lines: > > Create VM, install Elastic Search > Edit the Elastic Search config so it has the same cluster name as the > existing nodes > Enable the following options: > > elasticsearch_discovery_zen_ping_multicast_enabled = false > elasticsearch_discovery_zen_ping_unicast_hosts = 127.0.0.1:9300 > > > Start the new service > Restart the existing Graylog + Elastic Search services. > > Am I missing anything? > > Nathan > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/graylog2/85715b28-766e-4400-9424-91c411392c22%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
