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

Tenant Oplog Applier doesn't grab the RSTL before reserving oplog slots

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 5.0.0-rc3, 5.1.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • Labels:
    • Fully Compatible
    • ALL
    • v5.0
    • Repl 2021-06-28
    • 167

      The tenant oplog applier doesn't grab the RSTL via AutoGetOplog before reserving oplog slots here, the way it does elsewhere. This needs to be added.

      Currently, it's possible for the primary (on which the tenant oplog applier exists) to stepdown, but have the applier continue to run. This may cause a clash with the secondary oplog fetcher, and cause the stable timestamp to move ahead of the all durable timestamp, triggering an fassert.

            vishnu.kaushik@mongodb.com Vishnu Kaushik
            vishnu.kaushik@mongodb.com Vishnu Kaushik
            0 Vote for this issue
            4 Start watching this issue