getLastError should not be affected by no-op retries

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Won't Fix
    • Priority: Major - P3
    • None
    • Affects Version/s: 3.5.13
    • Component/s: None
    • Sharding
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      The n and upserted fields (maybe more) in the getLastError command response are reset by no-op retries of retryable write commands. Since the retries are logically tied to the original successful commands, they probably shouldn't affect the output of getLastError.

      Failing retryable_writes_jscore_passthrough tests:

      • bulk_legacy_enfore_gle.js

              Assignee:
              [DO NOT USE] Backlog - Sharding Team
              Reporter:
              Jack Mulrow
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: