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

legacy update path cleanup

    • Type: Icon: Improvement Improvement
    • Resolution: Unresolved
    • Priority: Icon: Minor - P4 Minor - P4
    • None
    • Affects Version/s: None
    • Component/s: Write Ops
    • None
    • Query Execution

      There are a few improvements to the update path for legacy writes (see receivedUpdate in instance.cpp) which we should consider.

      1. There is a separate WriteConflictException retry loop for the collection creation case, i.e. upsert into an empty collection. We should be able to consolidate this into a single retry loop.
      2. The catch block for WriteConflictException logs and then re-throws the exception if it is a multi-update. The UpdateStage, however, should be responsible for catching WriteConflictException in the multi-update case.

            Assignee:
            backlog-query-execution [DO NOT USE] Backlog - Query Execution
            Reporter:
            david.storch@mongodb.com David Storch
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: