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

multi_statement_transaction_abort.js should use explicit batch size for find

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 8.1.0-rc0, 8.0.0-rc17
    • Affects Version/s: None
    • Component/s: None
    • None
    • Replication
    • Fully Compatible
    • ALL
    • v8.0
    • Repl 2024-08-05, Repl 2024-08-19
    • 0

      SERVER-87285 introduced fuzzing of internalQueryFindCommandBatchSize which determines "The batch size used for find commands as a default if none is specified."

      This causes failures in multi_statement_transaction_abort.js when the batchSize is set to a value <= 3 as the collection contains 3 documents and the test asserts that the find returns a cursor ID of 0. With batchSize 1 or 2, we don't get all the docs back and so get a non-zero ID, with batchSize of 3, as SERVER-57067 describes, we also don't.

      Using an explicit batch size of 4 for this find should ensure the server always exhausts all the results and returns cursor ID 0.

            Assignee:
            kaitlin.mahar@mongodb.com Kaitlin Mahar
            Reporter:
            kaitlin.mahar@mongodb.com Kaitlin Mahar
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: