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

Details

    • Icon: Improvement Improvement
    • Resolution: Duplicate
    • Icon: Major - P3 Major - P3
    • None
    • None
    • Sharding
    • None
    • Fully Compatible
    • Sharding 2017-11-13

    Description

      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.

      Attachments

        Activity

          People

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

            Dates

              Created:
              Updated:
              Resolved: