[SERVER-86035] Avoid closing the connections for transaction write errors Created: 31/Jan/24 Updated: 05/Feb/24 |
|
| Status: | Needs Scheduling |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Abdul Qadeer | Assignee: | Backlog - Cluster Scalability |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Cluster Scalability
|
| Participants: |
| Description |
|
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. |