Hi Kristina Chodorow, it seems that the "READ" does not work as well
if 2 nodes of 3 nodes in a replica set are brought down. i got
"uncaught exception: count failed : {"errmsg" : "not master", "ok" :
0}
Any advice?
On Aug 3, 10:57 am, Kristina Chodorow <
krist...@10gen.com> wrote:
> If two members are down, the set becomes read-only (so, not exactly
> unavailable). This is to avoid multi-master conflicts in the case of
> network partitions.
>
> We assume each shard will be one replica set, that may be read-only in
> case of disaster. It's one of the tradeoffs of a stronger consistency
> model.
>
> On Mon, Aug 2, 2010 at 10:04 PM, David M <
da...@boxedice.com> wrote:
> > In a 3memberreplica set, if 2 of the members are down then the set
> > becomes unavailable. What's the reason for this?
>
> > In the documentation athttp://
www.mongodb.org/display/DOCS/Sharding+and+Failover
> > it says
>
> > "If the shard is configured as a replica set, with at least onemember
> > of the set in another data center, then an outage of an ensure shard
> > is extremely unlikely."
>
> >butthis is not the case because if there is only1memberin another