Uploaded image for project: 'Documentation'
  1. Documentation
  2. DOCS-10836

Docs for SERVER-31170: Add support for session and transaction number to benchRun

    • Type: Icon: Task Task
    • Resolution: Gone away
    • Priority: Icon: Major - P3 Major - P3
    • 3.6.0-rc0
    • Affects Version/s: None
    • Component/s: manual, Server
    • Labels:
      None

      Documentation Request Summary:

      Not sure if we document the benchRun parameters somewhere, but if we do we need to include the two new parameters listed in the description.

      Engineering Ticket Description:

      The benchRun utility is used by both mongo-perf and sys-perf. In order to test the performance of retryable writes we need to make benchRun use sessions and send transaction numbers.

      In order to achieve this, benchRun will be extended with the following options:

      • useSessions (bool) - when this option is enabled, benchRun will call startSession for each connection that it creates and will add the returned session id along with every command that it sends to the server.
      • useIdempotentWrites (bool) - when this option is enabled, benchRun will keep an always-incrementing transaction number for each workload thread and will send that as a txnNumber.

      Both these parameters may only be specified if useWriteCmd is true and will fail with a BadOptions error code otherwise.

      NOTE: The combination of sessionId/txnNumber makes the write retryable, but this ticket will not add any functionality to benchRun to actually retry since this is a much more involved task.

            Assignee:
            Unassigned Unassigned
            Reporter:
            kay.kim@mongodb.com Kay Kim (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved:
              6 years, 31 weeks, 1 day ago