If you clone a database and a document, due to an update, moves forward in memory, cloner might clone both the old and new document. When this happens, creating a unique index might fail. This change restarts the clone when this happens, and will abort after 3 failed cloning attempts.
…g message in appropriate cases.
Modified the initialization of the ok member variable of ReplicaSetMonitor::Node to true if conn smart pointer is not null. Conflicts: jstests/sharding/slaveok_routing.js
Authenticate connection to replica members with keyFile credentials when calling replSetGetStatus internally. Conflicts: client/dbclient_rs.cpp
SERVER-4750 prevent syncing to secondaries with a slavedelay greater than yourself Conflicts: db/repl/rs_initialsync.cpp jstests/replsets/slavedelay3.js
Signed-off-by: Eric Milkie <email@example.com>
…cessfully authenticates to web server Signed-off-by: Eric Milkie <firstname.lastname@example.org>
The 'compact' operation sequentially copies all the records in the namespace into a new extent. Since this operation creates no new data, the standard extent logarithmic sizing should not apply; the algorithm is only to accomodate data growth. Instead, we will start back at the beginning with the smallest extent size. This will allow for freed-extent reuse over multiple compacts. Note that the only way to have freed extents in a database is to run compact, so the first time you run it, there will always be new extents created. Subsequent compacts will potentially reuse the freed extents.
… change, explicitly check for shard versioning turned on
… (corrected backport)
…tch size" This reverts commit e50b2e2.
…icate field names by applying updates to the first duplicate field provided by BSONObjIteratorSorted and passing through the remaining duplicates