"If a majority of the replica set is inaccessible or unavailable to the
current primary, the primary will step down and become a secondary. The
replica set cannot accept writes after this occurs, but remaining members
can continue to serve read queries if such queries are configured to run on
Is this statement true? Unless I misunderstand the above statement, this
scenario seems very "BAD" to me. To me this statement is telling me that
if I have a Replica set with three members that spans three data centers;
i.e. data center 1 contains the primary member, data center 2 contains a
secondary member, and data center 3 contains a secondary member; and if
data centers 2 and 3 go down, then data center 1 will have the primary
member revert to being a secondary member. This would be very bad for a
production system running on data center 1. In this scenario, the primary
member would become a secondary member and no more write operations would
be allowed by the production system running on data center 1. Is this true?
Why would anyone want this behavior? I can see a situation where one would
want to take down data centers 2 and 3 for maintenance, or they might go
down for some kind of failure, but that should not affect the production
system running on data center 1. Can anyone please explain this statement
in more detail to me?
You received this message because you are subscribed to the Google Groups "mongodb-user"