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

getLastError should not be affected by no-op retries

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

      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:
            backlog-server-sharding [DO NOT USE] Backlog - Sharding Team
            Reporter:
            jack.mulrow@mongodb.com Jack Mulrow
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: