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

Add command parameter to specify max wait time for speculative majority reads

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.1.8
    • Affects Version/s: None
    • Component/s: Replication
    • None
    • Replication
    • Fully Compatible
    • v4.0, v3.6

      We would like to add a new command argument that specifies how long a client is willing to wait for data to become majority committed when doing a speculative majority read. This is primarily to work around the fact that getMore commands on tailable, awaitData cursors do not use maxTimeMS as a global command timeout. They instead use it as the amount of time to wait for new inserts before returning to the client. Since speculative majority waiting may happen after batch generation, there is no way currently to specify a time limit on speculative majority waiting in this case. The goal is to address this issue with a new parameter; something analogous to the wtimeout parameter of write concern.

            Assignee:
            backlog-server-repl [DO NOT USE] Backlog - Replication Team
            Reporter:
            william.schultz@mongodb.com William Schultz (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: