Collection validation for multikey data containing equivalent values can lead to false positive index inconsistencies even without hitting max memory usage

XMLWordPrintableJSON

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

      As described in SERVER-89845, hitting the max validation memory usage threshold would cause us to zero out buckets during the second phase of validation, which could lead to reporting a false positive extra index inconsistency. However, it appears that we can hit this without exceeding the max memory usage threshold.

      It was difficult to determine how this happens/reproduce this partially because we weren't logging type bits for indexKeys, and because of bloat in validate logs, but with SERVER-113567 and SERVER-113288 addressing these issues it should be possible to make more headway the next time this happens.

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

              Created:
              Updated: