Uploaded image for project: 'WiredTiger'
  1. WiredTiger
  2. WT-6348

MongoDB test is failing reporting that index counts are incorrect

    • Type: Icon: Build Failure Build Failure
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None

      As described by milkie:

      In this failure, an index on test13_fsmdb0.create_capped_collection_maxdocs0_2 is validated successfully multiple times, but at some point, validation fails (only on the primary node), with three dangling index table records with no corresponding collection table records. Presumably these index records were deleted (in transactions that also deleted their collection table counterparts), but came back into visibility at some point afterward.

      This is related to capped collections, so we should check whether the data visibility issue is related to maintaining indexes on secondary indexes and using mixed mode timestamp writes.

            Assignee:
            backlog-server-storage-engines [DO NOT USE] Backlog - Storage Engines Team
            Reporter:
            alexander.gorrod@mongodb.com Alexander Gorrod
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: