Commits on Oct 5, 2012
  1. SERVER-4237 Make disk/repair5.js use startMongodTest instead of start…

    …MongoProgram so running with auth works
    stbrody committed Oct 5, 2012
  2. Merge pull request #310 from daveh86/SERVER-7050

    Fix for SERVER-7050
    IanWhalen committed Oct 5, 2012
  3. Merge branch 'SERVER-7272'

    renctan committed Oct 5, 2012
  4. buildbot stale_clustered.js also need to check whether mongos knows a…

    …bout new conns, pending SERVER-7274
    Greg Studer committed Oct 5, 2012
  5. buildbot stale_clustered.js slaveOk conn shouldn't be retried, but re…

    …gular conn should
    Greg Studer committed Oct 5, 2012
  6. Fix for SERVER-7050

    daveh86 committed Oct 5, 2012
Commits on Oct 4, 2012
  1. SERVER-7253 use macro for snprintf on Windows instead of function poi…

    Call _snprintf on Windows or snprintf on other platforms directly instead
    of through a statically initialized function pointer.  Windows code was
    calling sprintf_s, but _snprintf works fine and is already used in other
    places in the code.
    tadmarshall committed Oct 4, 2012
  2. SERVER-1929 Remove unused heartbeat options from stepdown logic

    Fixed test because stepdown is so much faster that the connection is dead
    by the time ismaster is called.
    kchodorow committed Oct 4, 2012
  3. SERVER-7257 this ticket is manifesting in checkAllVersions(). this ch…

    …ange is a small mitigation to just
    tell you what shard failed in checkAllVersions. So it doesn't fix the root version but should be
    incrementally helpful. The real solution is probably to do some sort of ShardConnectionException or
    something where at throw time the shard is known and its identity bundled with the error itself.
    dwight committed Oct 4, 2012
  4. SERVER-7220 only an incremental improvement so keep ticket open. add to

    $err object a shard: field in certain cases to help user know where the
    problem context is. q: Is it ok to add such a field to the $err object?
    dwight committed Oct 4, 2012
  5. SERVER-5175 Need "failpoints" system to facilitate testing core server

    Step 1: Implement and test the FailPoint class
    renctan committed Sep 19, 2012
Commits on Oct 3, 2012
  1. clarify error message. in mongos if you get this message it's pretty …

    …unclear as a user what is wrong. added the lists of hosts for the clusterconnection so you know what specifically is down. ideally we would say 'all config servers down: their_names' if that is what is wrong as that would be clearer but that would go somewhere up the stack so this is still suboptimal but an improvement.'
    dwight committed Oct 3, 2012
  2. SERVER-6671 add a 'v' version field to each oplog document

    The version field will allow us to detect the primary's version.
    We need to know which version because only newer primary oplog streams
    should prevent a secondary from enforcing unique index constraints
    in initial sync or recovering states.  The version field will also be
    useful in the future when we want to make schema changes in the oplog.
    milkie committed Oct 3, 2012
Commits on Oct 2, 2012