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

Make all primary durable timestamp updates go through the JournalListener

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.3.4
    • Affects Version/s: None
    • Component/s: Storage
    • None
    • Fully Compatible
    • Execution Team 2020-02-24
    • 0

      waitForWriteConcern is sometimes setting the last durable timestamp manually, as well as implicitly by calling into the storage engine for durability.

      These should be consolidated for ease of understanding, because the current state is confusing; and must be done in order to pick up the correct timestamp in getToken for setting the durable timestamp.

            Assignee:
            dianna.hohensee@mongodb.com Dianna Hohensee (Inactive)
            Reporter:
            dianna.hohensee@mongodb.com Dianna Hohensee (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: