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

Make waiting for the truncate point in waitForWriteConcern for single voter replica sets obey wtimeout

XMLWordPrintableJSON

    • Type: Icon: Task Task
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Storage
    • Labels:
      None
    • Replication
    • Execution Team 2020-06-29

      This work is the result of adding waiting for the truncate point in SERVER-46186.

      The code design should be made with consideration to SERVER-45847 and SERVER-45792. Currently we do not obey writeConcern's wtimeout for flushing the journal or waiting for the truncate point (the oplog no holes point).

      This ticket must also unmodify the majority_writes_wait_for_all_durable_timestamp.js test that SERVER-46186 modified to explicitly use

      {j: false}

      to get a writeConcern wtimeout to work.

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

              Created:
              Updated: