Avoid encoding the overflow document twice when a batched write command is split

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Performance, Write Ops
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      As we generate a batched write command we encode the next operation and add it to the command. If that operation caused the command to overflow the maximum command size then the write command is returned without that operation. As we generate the next message we will re-encode the same operation. We should save the encoded operation (or encode the operation elsewhere) to avoid ever encoding the same operation twice.

            Assignee:
            Unassigned
            Reporter:
            Shane Harvey
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: