Contents

# Latest secondary's lastWriteDate is used normally with read preference tags.
---
heartbeatFrequencyMS: 25000  # 25 seconds.
topology_description:
  type: ReplicaSetNoPrimary
  servers:
  - &1
    address: a:27017
    type: RSSecondary
    avg_rtt_ms: 5
    lastUpdateTime: 0
    maxWireVersion: 5
    lastWrite: {lastWriteDate: {$numberLong: "25002"}}
    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.
    tags:
      data_center: nyc
  - &3
    address: c:27017
    type: RSSecondary
    avg_rtt_ms: 5
    lastUpdateTime: 0
    maxWireVersion: 5
    lastWrite: {lastWriteDate: {$numberLong: "1"}}  # Too stale.
    tags:
      data_center: nyc
  - &4
    address: d:27017
    type: RSSecondary
    avg_rtt_ms: 5
    lastUpdateTime: 0
    maxWireVersion: 5
    lastWrite: {lastWriteDate: {$numberLong: "2"}}
    tags:
      data_center: tokyo  # No match.
read_preference:
  mode: SecondaryPreferred
  maxStalenessMS: 50000
  tag_sets:
  - data_center: nyc
suitable_servers:
- *2
in_latency_window:
- *2

Version data entries

2 entries across 2 versions & 1 rubygems

Version	Path
mongo-2.4.0.rc1	spec/support/max_staleness/ReplicaSetNoPrimary/SecondaryPreferred_tags.yml
mongo-2.4.0.rc0	spec/support/max_staleness/ReplicaSetNoPrimary/SecondaryPreferred_tags.yml