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

ConvertToCappedCoordinator may leave dirty metadata on the sharding catalog when interrupted by multiple stepdown events

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

      The "commit to the sharding catalog" phase of ConvertToCappedCoordinator  defines a conditional multi-step clean up process of partial writes performed in a previous attempt that first removes the entry from config.collections and later deletes the related config.chunks documents. Nevertheless, if a second step-down occurs between these two steps, the next retry won't perform any cleanup at all, since the initial condition will evaluate to false.

            Assignee:
            pierlauro.sciarelli@mongodb.com Pierlauro Sciarelli
            Reporter:
            paolo.polato@mongodb.com Paolo Polato
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: