[SERVER-40988] Log metrics on mongod when slow two phase commit completes Created: 03/May/19 Updated: 29/Oct/23 Resolved: 10/Jun/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.2.0-rc1, 4.3.1 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Jack Mulrow | Assignee: | Esha Maharishi (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Backport Requested: |
v4.2
|
||||
| Sprint: | Sharding 2019-05-20, Sharding 2019-06-03, Sharding 2019-06-17 | ||||
| Participants: | |||||
| Description |
|
When a TransactionCoordinator makes its commit/abort decision externally available, if the commit took longer than the default 100ms threshold, log the slow commit metrics as described in this section of the diagnostics scope. The metrics logged should be re-usable from |
| Comments |
| Comment by Githook User [ 10/Jun/19 ] |
|
Author: {'name': 'Esha Maharishi', 'email': 'esha.maharishi@mongodb.com', 'username': 'EshaMaharishi'}Message: (cherry picked from commit b630e9dfb3772c069bda2cbf8f6cc3ec170c7d5b) |
| Comment by Githook User [ 10/Jun/19 ] |
|
Author: {'name': 'Esha Maharishi', 'email': 'esha.maharishi@mongodb.com', 'username': 'EshaMaharishi'}Message: |