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

Allow secondaries to automatically refresh sharding metadata

    • Type: Icon: Improvement Improvement
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Labels:
    • Catalog and Routing

      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

            backlog-server-catalog-and-routing [DO NOT USE] Backlog - Catalog and Routing
            renato.riccio@mongodb.com Renato Riccio
            0 Vote for this issue
            5 Start watching this issue