spec/support/max_staleness/ReplicaSetNoPrimary/Secondary.yml in mongo-2.4.0.rc1 vs spec/support/max_staleness/ReplicaSetNoPrimary/Secondary.yml in mongo-2.4.0

@@ -8,20 +8,20 @@
     address: a:27017
     type: RSSecondary
     avg_rtt_ms: 5
     lastUpdateTime: 0
     maxWireVersion: 5
-    lastWrite: {lastWriteDate: {$numberLong: "25002"}}
+    lastWrite: {lastWriteDate: {$numberLong: "125002"}}
     tags:
       data_center: tokyo  # No match, but its lastWriteDate is used in estimate.
   - &2
     address: b:27017
     type: RSSecondary
     avg_rtt_ms: 5
     lastUpdateTime: 0
     maxWireVersion: 5
-    lastWrite: {lastWriteDate: {$numberLong: "2"}}  # 25 sec stale + 25 sec heartbeat <= 50 sec maxStaleness.
+    lastWrite: {lastWriteDate: {$numberLong: "2"}}  # 125 sec stale + 25 sec heartbeat <= 150 sec maxStaleness.
     tags:
       data_center: nyc
   - &3
     address: c:27017
     type: RSSecondary
@@ -40,10 +40,10 @@
     lastWrite: {lastWriteDate: {$numberLong: "2"}}
     tags:
       data_center: tokyo  # No match.
 read_preference:
   mode: Secondary
-  maxStalenessMS: 50000
+  maxStalenessSeconds: 150
   tag_sets:
   - data_center: nyc
 suitable_servers:
 - *2
 in_latency_window: