Investigate why PBT testing did not detect insertion of duplicate data

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Storage Execution
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      In SERVER-131302, an uncaught StaleConfig exception could result in more measurements than expected being inserted into a time-series collection. The ask for this ticket is to evaluate why existing PBT coverage did not detect it and close the testing gap on issues of this nature.

      Validate does not currently detect duplicate measurements (addressed by SERVER-133152), and the insert command itself would succeed in SERVER-131302. One idea for how to detect this is to add testing infrastructure that checks how many documents were actually inserted into the collection and match it against how many documents we tried to insert (in SERVER-133152, the numInserted field in the insert command response did not count the duplicate measurements).

            Assignee:
            Unassigned
            Reporter:
            Damian Wasilewicz
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: