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

Add the explicit replay protection to the commit phase of the sharding ConvertToCappedCoordinator

    • Type: Icon: Improvement Improvement
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 8.0.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • Catalog and Routing
    • Fully Compatible
    • CAR Team 2024-03-18, CAR Team 2024-04-01

      The "commit to the config catalog" phase of the Sharding convertToCapped DDL contains a series of remote writes to the config server, some of which are not idempotent: today, the protection against "replay side effects on node stepdown" is guaranteed by the fact that the first remote write in the sequence is implemented as a transaction, but this exposes the code to potential future regressions.

      To avoid this, a simple call to _performNoopRetryableWriteOnAllShardsAndConfigsvr may be added as the first instruction of the phase.

            Assignee:
            paolo.polato@mongodb.com Paolo Polato
            Reporter:
            paolo.polato@mongodb.com Paolo Polato
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: