Avoid closing the connections for transaction write errors

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Query Execution
    • QE 2024-09-16, QE 2024-09-30, QE 2024-10-14, QE 2024-10-28, QE 2024-11-11, QE 2024-11-25, QE 2024-12-09, QE 2024-12-23, QE 2025-01-06, QE 2025-01-20, QE 2025-02-03, QE 2025-02-17, QE 2025-03-03, QE 2025-03-17
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      During the investigation of SERVER-85857, we found that such a code path closing connections exists in two other places (here and here) where we abort the batch due to transaction write errors. WriteConflict errors are reasonably frequent in transactions and during high write rates or high CPU usage we should be able to improve the performance by a considerable number.

            Assignee:
            Unassigned
            Reporter:
            Abdul Qadeer
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated: