Move writeConflictRetry to the Storage Execution team

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Catalog and Routing
    • 1
    • 🟦 Shard Catalog
    • None
    • None
    • None
    • None
    • None
    • None

      writeConflictRetry is in exception_util.h, which is owned by CAR, even though we don't own the algorithm itself. This is a source of confusion as to which team should be involved when dealing with this loop.

      After discussing with kaloian.manassiev@mongodb.com, we think that low level retry loop should be owned by Storage Execution, so we should move it out to a separate file owned by the right team.

            Assignee:
            Unassigned
            Reporter:
            Daniel Gomez Ferro
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: