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.
Only attempt to clear a query's pattern if the query is satisfiable for the specified index type.
…g message in appropriate cases.
SERVER-4750 prevent syncing to secondaries with a slavedelay greater than yourself Conflicts: db/repl/rs_initialsync.cpp jstests/replsets/slavedelay3.js
… change, explicitly check for shard versioning turned on
…icate field names by applying updates to the first duplicate field provided by BSONObjIteratorSorted and passing through the remaining duplicates
…list obey it
…ary after first sharding
…ime. This fix changes mongos to stop limiting the shards to send to after the first $in clause - possibly sending the query to more shards than necessary, but saving time. SERVER-4745.
…hould disappear from config
…n of unhelpful recorded plans
tested with a 2.2 shell to make sure it works
…invalid on yield recovery
… fails; this patch violates the QueryOp abstraction a bit, but we are replacing that code soon anyway
… trying slaveok'd connection