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

Refresh the in-memory metadata cache on secondaries when invalidated by a primary metadata change

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Won't Fix
    • Icon: Major - P3 Major - P3
    • None
    • None
    • Sharding
    • None
    • Fully Compatible
    • Sharding 2017-08-21

    Description

      The current secondary behavior is just to invalidate the secondary's metadata so that the next request to the secondary causes an in-memory refresh. Refreshes require contacting the shard primary, in case the primary is not up to date either and must refresh from the config servers.

      A secondary that has the up to date metadata persisted, but hasn't serviced requests in a long while so the up to date metadata hasn't been loaded into memory, can get stuck when it receives a request while either there is no primary or the primary cannot be contacted. To alleviate this situation, we will proactive reload the in-memory cache on receipt of metadata updates. This is a performance improvement.

      Attachments

        Activity

          People

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

            Dates

              Created:
              Updated:
              Resolved: