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

Legacy shard collection path waits on wrong opTime to be majority committed (5.0 and older)

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 5.0.15
    • Sharding
    • None
    • Fully Compatible
    • ALL
    • Sharding EMEA 2022-11-14, Sharding EMEA 2022-11-28
    • 55

    Description

      Similarly to SERVER-56556, the 4.4 legacy shard collection patch waits for majority write concern after creating the shard index.

      The problem is that if the index was already created no write will be performed , in this case the last op time on the current client could be a very old op time, associated with the last write performed by a previous operation.

      Attachments

        Activity

          People

            pol.pinol@mongodb.com Pol Pinol
            sergi.mateo-bellido@mongodb.com Sergi Mateo Bellido
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: