We have the same issue here, we actually have 4 Graylog2 servers, two are dedicated search nodes for the web interface (one of which is the master) and the other two are dedicated for inputs.
If I ever have the master node offline, the web interface reports it cannot contact a Graylog2 master node and users cannot log in nor use the interface, however inputs of course keep accepting data and streams are still processed. I have attached a screen dump of the error. What would be ideal is if there was a similar setting like Elasticsearch where you can elect nodes that *can* be masters and an election is performed automatically by the Graylog2 service. On Wednesday, 18 June 2014 22:22:55 UTC+10, [email protected] wrote: > > Hello, > > I thought, I could setup an HA-Graylog2-Cluster. But there has to be only > a single master node, otherwise, I get this message: > > Multiple graylog2-server masters in the cluster a few seconds ago > There were multiple graylog2-server instances configured as master in your > Graylog2 cluster. The cluster handles this automatically by launching new > nodes as slaves if there already is a master but you should still fix this. > Check the graylog2.conf of every node and make sure that only one instance > has is_master set to true. Close this notification if you think you > resolved the problem. It will pop back up if you start a second master node > again. > > If I ignore this message, things seem to work - but if the master node > dies, you can't login to web-interface anymore :-( > > Is there a way to have "real" High-Availability? > > regards > > Cornelius > -- You received this message because you are subscribed to the Google Groups "graylog2" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
