Try it out. :) Shutdown the master and see what happens. Graylog2 should handle that transparently and will be notified about the new master.
On Thu, Mar 6, 2014 at 3:56 PM, Robert <[email protected]> wrote: > There are a lot of hits on Google for creating a three node replica set with > MongoDB and using it for Graylog2. For more information: > http://docs.mongodb.org/manual/core/replica-set-architecture-three-members/. > I understand I can add the following line to graylog2.conf: > > mongodb_replica_set = host1:27017,host2:27017,host3:27017 > > What I don't understand is how I should use this setting if I want to have a > failover solution. Lets say the master host in the MongoDB replica set > fails, a election starts between the two hosts that are left and a new > master will be elected. How should Graylog2 know which node will become the > master? This is of importance because the master is the only host that will > accept write actions, or am I wrong here? > > Regards, > Robert > > -- > 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. -- 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.
