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

Allow secondaries to automatically refresh sharding metadata

    XMLWordPrintableJSON

Details

    • Icon: Improvement Improvement
    • Resolution: Duplicate
    • Icon: Major - P3 Major - P3
    • None
    • None
    • None
    • Catalog and Routing

    Description

      Currently secondaries are refreshing sharding metadata only when receiving a query with the sharding version (from mongos or via mirrored reads).

      This means that if a secondary that did not receive any query become primary (for example an hidden node that is made primary after a rs config change) will need to full refresh the metadata and therefore possibly heavily impacting the query performance.

      Would be nice to force metadata refresh of all secondaries every time there is a metadata change (like is happening on the primary) and not wait for an upcoming queries

      Attachments

        Activity

          People

            backlog-server-catalog-and-routing Backlog - Catalog and Routing
            renato.riccio@mongodb.com Renato Riccio
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: