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

Investigate config.transactions collection and index validation

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 6.3.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • Labels:
    • Fully Compatible

      When implementing validation for CSI, we found two collections which apparently do not update indexes when written to, namely:

      • local.replset.oplogTruncateAfterPoint
      • config.transactions

      geert.bosch@mongodb.com commented in a discussion with charlie.swanson@mongodb.com that such behavior is not unexpected in local.replset.oplogTruncateAfterPoint , but we don't know for sure about config.transaction. We'd like to get someone to confirm this.

      We have a failpoint which puts CSI on all collections for testing, but these two collections are exempt (via this helper function). We want to be sure that is the correct thing to do.

            mohammad.dashti@mongodb.com Mohammad Dashti (Inactive)
            colin.stolley@mongodb.com Colin Stolley
            0 Vote for this issue
            5 Start watching this issue