Don't fetch oplog entries for retries of executed inserts or deletes

XMLWordPrintableJSON

    • Fully Compatible
    • Sharding 2017-10-23, Sharding 2017-11-13
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Right now retrying a successful write requires fetching the oplog entry for each completed statement. Since the oplog entry isn't necessary to build the response for inserts and deletes (both just set the n field to 1, here and here), Session::checkStatementExecuted can skip fetching the oplog entry for those commands, which should make no-op retries faster.

            Assignee:
            Kaloian Manassiev
            Reporter:
            Jack Mulrow
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: