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

Investigate potential gaps in FTDC and a loss in retention when introducing the embedded router collectors

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Unresolved
    • Icon: Major - P3 Major - P3
    • None
    • None
    • None
    • Catalog and Routing

    Description

      When introducing more collectors to the FTDC machinery, there is the possibility to create gaps and a loss in retention. In other words, there are some heavy/intensive collectors (e.g. serverStatus) that will make the FTDC machinery to recollect data each time in a bigger interval, producing a regression in the dimension / richness of the data (more gaps). 

      When introducing the embedded router collectors, for instance, the serverStatus will be called twice, one for the shard and one for the router, and this can reproduce the problems explained.

      The goal of this ticket is to see if these cases are being reproduced and, if applies, how to solve them. 

      Attachments

        Activity

          People

            backlog-server-catalog-and-routing Backlog - Catalog and Routing
            pol.pinol@mongodb.com Pol Pinol
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated: