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

Chunk refresh from a secondary does not wait for majority writeConcern while flushing

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 8.0.0-rc0, 6.0.15, 7.0.8, 5.0.27, 7.3.2
    • Affects Version/s: 7.0.6, 5.0.25, 4.4.29, 6.0.14, 7.3.0-rc3
    • Component/s: None
    • None
    • Catalog and Routing
    • Fully Compatible
    • ALL
    • v7.3, v7.0, v6.0, v5.0
    • CAR Team 2024-03-04, CAR Team 2024-03-18
    • 5
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Consider the following scenario:

      • Secondary schedules a refresh of the chunks on the primary
      • Primary successfully writes the refresh locally
      • Before this operation gets replicated and we advance the stable timestamp we stepDown the primary

      As a result of this, since the new primary will not be inclusive of the refresh the returned opTime is completely meaninglesss since it will be associated to arolled back entry.

            Assignee:
            jordi.olivares-provencio@mongodb.com Jordi Olivares Provencio
            Reporter:
            jordi.olivares-provencio@mongodb.com Jordi Olivares Provencio
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved:
              None
              None
              None
              None