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

Migrate printShardingStatus shell helper logic to database command

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

      The sh.status() and db.printShardingStatus() shell helpers both call the getPrintableShardingStatus mongosh function.
      This function is fairly complicated and does a bunch of aggregations and data manipulations to create the sh.status() output. The goal of this ticket is to analyze the getPrintableShardingStatus logic and figure out if we could introduce some new commnad/aggregation stage to simplify the gathering of this information.

      Exposing those intermediate commands would allow customer to retrieve this information more easily also from other drivers (aka outside of the mongosh)

            backlog-server-catalog-and-routing [DO NOT USE] Backlog - Catalog and Routing
            alex.bevilacqua@mongodb.com Alex Bevilacqua
            2 Vote for this issue
            18 Start watching this issue