[SERVER-37756] add logging for the amount of time spent blocked on a prepare conflict Created: 25/Oct/18 Updated: 29/Oct/23 Resolved: 16/Sep/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Diagnostics, Replication |
| Affects Version/s: | None |
| Fix Version/s: | 4.3.1 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Pavithra Vetriselvan | Assignee: | Haley Connelly |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | SWDI, prepare_diagnostics, prepare_optional | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Execution Team 2019-09-23 |
| Participants: |
| Description |
|
Currently, long running operations show up in currentOp along with the locks that they held here We would like to do something similar for long running reads that were blocked on a prepare conflict. |
| Comments |
| Comment by Haley Connelly [ 16/Sep/19 ] | |
|
Added prepareConflictDuration to log the total time spent blocked on prepare conflicts when it is nonzero.
| |
| Comment by Githook User [ 16/Sep/19 ] | |
|
Author: {'name': 'Haley Connelly', 'username': 'haleyConnelly', 'email': 'haley.connelly@10gen.com'}Message: | |
| Comment by Bruce Lucas (Inactive) [ 29/Oct/18 ] | |
|
I'm not sure what exactly is missing and what is to be added. In general, every running operation should show up in currentOp in some form. If the reads mentioned are not showing up at all, then in my view it's required to fix that. If they are showing up but have missing information relating to what they're blocked on, then it's highly desirable that that should be added.
So short answer is yes, required or highly desirable depending on the details. | |
| Comment by Gregory McKeon (Inactive) [ 29/Oct/18 ] | |
|
kelsey.schubert bruce.lucas@mongodb.com how helpful do you think this would be for diagnostics? |