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

Factor in possible error response size when building unordered bulkWrite batches

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Gone away
    • Icon: Major - P3 Major - P3
    • None
    • None
    • None
    • None
    • Replication

    Description

      This ticket is being filed speculatively in the event that we end up not returning a cursor from bulkWrite. If we keep the cursor, then I believe we can just remove the TODO and close this ticket.

      In the getWriteSizeFn passed to targetWriteOps for non-bulkWrite batched writes, we ensure that for unordered writes we do not build any batches that could possibly generate an error response too large to fit into a single reply.
      I think we don't need this for now in the equivalent bulkWrite logic due to the cursor response allowing us to return a response of arbitrarily large size, but we could end up needing this if we change plans, so I wanted to file this ticket so we remember that.

      Attachments

        Activity

          People

            backlog-server-repl Backlog - Replication Team
            kaitlin.mahar@mongodb.com Kaitlin Mahar
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: