On Wed, May 16, 2012 at 5:17 AM, Chitra <[email protected]> wrote: > Distributed Database Arbiter for primary only
So if primary is shutdown, system loses both a mongo db and a mongo arbiter. This means secondary cannot decide on it's own to become master. This is an unfortunate reality for mongo and how it elects masters. If you stop the mongo db service on the primary or you shutdown the secondary machine altogether, you should fail-over working. At some point, you'll want to setup a 3 node cluster and install either arbitor or a mongo db on the third system and then you can take out to primary completely and see what happens. _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev/
