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

Define specifications for resultant BSON format when the routing capabilities for MongoD are enabled

    • Type: Icon: Task Task
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Catalog and Routing
    • CAR Team 2024-03-04

      The `t2` tool needs to be adapted to be able to graphically represent the role categorization introduced by SERVER-82931 & SERVER-82034.

      The current implementation of the BSON object to use for `t2` is:

      {
         "start" : Date_t,
         "collector1" : {         
            "start" : Date_t, 
            "data" : { ... }  
            "end" : Date_t,
         },
         "collector2" : { ... },
         ...,
         "end" : Date_t,
      }
      

      After SERVER-82034, each collector data will be under a parent field representing a role categorization (common, shard or router), resulting in a new BSON object format that `t2`is not able to parse.

      The objective of this ticket is to

      • Write all the specifications for the new BSON object format.
      • Open a ticket and assign it to the STAR team to change `t2` in favor of the linked specifications.

            Assignee:
            aitor.esteve@mongodb.com Aitor Esteve Alvarado
            Reporter:
            pol.pinol@mongodb.com Pol Pinol
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: