Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-31713

Persisted routing table refreshes cause in-memory routing table invalidations on primaries and secondaries, but should only do so on secondaries

XMLWordPrintableJSON

    • Type: Icon: Improvement Improvement
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Sharding
    • None
    • Fully Compatible
    • Sharding 2017-11-13

      We have a couple config.cache.collections field signals on which shard nodes take actions to invalidate their in-memory routing table cache. This is only needed on secondaries, now, so this code should only run on secondaries.

            Assignee:
            dianna.hohensee@mongodb.com Dianna Hohensee (Inactive)
            Reporter:
            dianna.hohensee@mongodb.com Dianna Hohensee (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: