The behavior for a list of mongoses is changed from "high availability" to "load balancing". Before, the client connected to the lowest-latency mongos in the list, and used it until a network error prompted it to re-evaluate all mongoses' latencies and reconnect to one of them. In PyMongo 3, the client monitors its network latency to all the mongoses continuously, and distributes operations evenly among those with the lowest latency. See high_availability.rst. |
||
|---|---|---|
| .. | ||
| aggregation.rst | ||
| authentication.rst | ||
| bulk.rst | ||
| copydb.rst | ||
| custom_type.rst | ||
| geo.rst | ||
| gevent.rst | ||
| gridfs.rst | ||
| high_availability.rst | ||
| index.rst | ||
| mod_wsgi.rst | ||