[SERVER-82229] Separate out aborted reads from aborted writes in serverStatus Created: 18/Sep/23 Updated: 26/Oct/23 |
|
| Status: | Open |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Judah Schvimer | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | former-storex-namer, perf-improvement, supportability | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Storage Execution
|
||||
| Sprint: | Joker - StorEng - 2023-10-17 | ||||
| Participants: | |||||
| Description |
|
Transaction aborts are included in server status. We always abort reads in the server, which makes it hard to see when writes are getting rolled back for abnormal reasons |
| Comments |
| Comment by Judah Schvimer [ 16/Oct/23 ] |
|
Great point! I moved it over to being a SERVER ticket. |
| Comment by Will Korteland [ 16/Oct/23 ] |
|
judah.schvimer@mongodb.com would you be able to provide a little more context on this one please? This reads like it should be a server ticket (since WT doesn't touch that "server status" field in FTDC, and I think WT already has stats around aborts). |